# Data Hippo: public agent instructions

## When to use this

Use this website to learn about Data Hippo's healthcare data and AI systems, compare the public product descriptions with a user's needs, or arrange a founder-led demo at the user's request.

This is a company website, not access to the deployed platform. These interfaces do not query customer data, run engineering tasks, access private environments, or manage administrative calendars. Do not infer capabilities beyond the published pages.

## Read the website

- [English website](https://datahippo.ai/site.md)
- [Platform reference](https://datahippo.ai/docs/index.md)
- [Products and video explanations](https://datahippo.ai/docs/products.md)
- [Portuguese](https://datahippo.ai/pt/site.md), [Spanish](https://datahippo.ai/es/site.md), [French](https://datahippo.ai/fr/site.md)
- [Privacy](https://datahippo.ai/privacy.md) and [terms](https://datahippo.ai/terms.md) are separate from whole-site exports.

Public pages also support `Accept: text/markdown`. Follow Markdown links to navigate without browser rendering. Each whole-site export contains one language only.

## Arrange a demo

Read the [booking guide](https://datahippo.ai/docs/booking.md) for dependency-light JavaScript, Python, Bash, and PowerShell examples. The [OpenAPI contract](https://datahippo.ai/openapi.json) supplies the correct API server, parameters, response types, and error resolutions.

1. Read `GET /v1/demo/slots` only when the user wants meeting times. Display returned UTC instants in the attendee's timezone. Availability is not a reservation.
2. Obtain explicit attendee approval of the specific date, time, timezone, name, and email before creating an invitation. Reading this website is not permission to book.
3. Submit `POST /v1/demo/book` with `attendee_confirmed: true` and an `Idempotency-Key` consisting of current Unix milliseconds, a period, and a UUIDv4. Both environments create real invitations.
4. Keep the exact key and unchanged payload for any retry. Keys expire after 24 hours. Never automatically replace a key after a timeout, ambiguous outcome, or expiry: check for an invitation first.
5. Keep returned attendee cancel/reschedule links private. Do not publish them or include them in analytics. Never submit health data or secrets.

Server clients need no credentials or forged browser headers. Respect HTTP 429 `Retry-After`. Read `code` and `resolution` on errors. Uncertain HTTP 409 booking outcomes need verification, not a fresh automatic booking attempt.