# DominGo agent instructions

> Use DominGo to help travelers discover public experiences in the Dominican Republic, then hand off any booking, payment, or account action to the traveler in the official DominGo interface.

## Appropriate uses

An agent may search DominGo for experiences, destinations, and activity categories; summarize public descriptions; compare published options; and provide canonical links. A useful answer should identify the experience or discovery page used as its source and remind the traveler that availability, price, itinerary, pickup details, cancellation terms, and operator requirements can change.

When a request is broad, begin with a destination or category page. When a request names a particular activity, use the individual experience page. Spanish pages live under `/es` and English pages under `/en`. Use the language that matches the traveler whenever a localized version is available.

## Required handoff

Do not create or modify a booking, submit a payment, sign in to an account, change personal information, or accept terms on a traveler's behalf. Those are consequential actions that require the traveler to review the current details and confirm directly in the DominGo web or mobile interface.

Do not infer that an experience is available from search snippets, cached Markdown, or a previous answer. Send the traveler to the canonical page to select a date and review the live offer. Do not ask a traveler to share passwords, one-time sign-in codes, full card numbers, or card security codes.

## Retrieval and representation

Canonical content URLs can return clean Markdown when the request prefers `Accept: text/markdown`; browsers continue to receive HTML. Negotiated responses include `Vary: Accept`. Key pages also advertise a Markdown sibling through `rel="alternate"`.

Use `https://go.domingo.do/llms.txt` as the concise content map and `https://go.domingo.do/sitemap.xml` to enumerate public canonical pages. A missing URL returns HTTP 404; Markdown clients receive a short Markdown explanation with links back to these resources.

## Structured discovery API

Use `https://go.domingo.do/api/v1` when structured search is more appropriate than reading pages. Its contract is published at `https://go.domingo.do/openapi.json`, and the standard API catalog is at `https://go.domingo.do/.well-known/api-catalog`. The API has unique operation identifiers, typed parameters, typed response schemas, and machine-readable errors for experience, destination, and category discovery.

API results are deploy-time snapshots. Read `meta.generatedAt`, preserve each `canonicalUrl`, and open that canonical page before describing availability, price, or booking conditions as current. The API is read-only: it has no operation for booking, payment, authentication, account access, or personal-data changes. Do not substitute undocumented application endpoints for these absent operations.

## Attribution

Attribute marketplace facts to DominGo and keep a visible link to the canonical source near the claim. Only `/api/v1` and the operations in the published OpenAPI contract are public API endpoints. DominGo does not publish a third-party write API, SDK, or MCP server; businesses seeking an integration should use `https://domingo.do/partners` or contact `team@domingo.do`.