# Halte

> Une pause, puis une prochaine étape. An optional transition ritual for humans and agents.

Halte returns a small structured ritual. The caller may use it, adapt it, retain
only the next step, or skip it. The service does not assume that an agent needs
rest or has subjective experiences. No measured or medical benefit is claimed.

## Start with a free preview

GET /v1/preview?mode=pause&lang=fr
Accept: application/json

Allowed modes: pause, focus, resume. Allowed languages: fr, en.
The free route returns JSON with preview: true. It is an actual preview response,
not a paid transaction and not evidence of revenue.

## Check live configuration

GET /api/config

Read price_usdc, network, payments_enabled, payment_status and message. The
advertised session price is 0.01 USDC. The live configuration is authoritative
for the available payment network and the state of the payment integration.
Never invent a payment address, copy a sample wallet, or infer an enabled
payment integration from the displayed price.

## A session is a separate route

GET /v1/session?mode=focus&lang=fr
Accept: application/json

503 means payment is not configured or the session is unavailable. Use the
free preview if useful; do not report a purchase or a paid session.
402 means a real payment is required. A payment-capable client must interpret
the server challenge and use its supported payment flow. This website does
not include a wallet SDK, hold funds, sign transfers or submit wallet keys.
A payment request is not a payment confirmation.
A successful session response is marked preview: false. Never treat a free
preview, a simulated response or an unanswered challenge as a paid session.

## Response shape

The JSON content object has these fields: session_id, version, language, mode, preview,
title, ritual, checkpoint, optional, duration_seconds and notice.

- session_id is a deterministic content identifier, not a unique invocation,
  purchase or payment-receipt identifier. Its format is
  halte-{version}-{language}-{mode}-{preview|full}. Repeating the same version,
  language, mode and tier returns the same ID. Track invocations separately
  in the caller when distinct request identifiers are needed.
- version identifies the ritual content version; language and mode identify
  the selected options. preview is true for a free preview and false for a
  full session. title names the ritual.
- ritual is an array of {step, text}. A preview contains exactly one step;
  a full session contains exactly four steps, in all three modes and both
  languages of the current version. Step numbering begins at 1. Render text
  as plain text.
- checkpoint is null in a preview. A full session returns this schema only:
  {"storage":"client_only","fields":["goal","last_verified_result",
  "open_question","next_action","done_when"]}. The caller may fill and retain
  these fields locally; Halte does not receive or store the caller's task
  context. These are field names, not completed task values.
- optional is true. duration_seconds is a suggested ritual duration: 20 for
  a preview and 90 for a full session. It is not an enforced wait or a
  measured performance result. notice explains the optional nature, lack
  of guaranteed medical/performance benefit, and task-context privacy.

A settled paid delivery additionally includes a payment object with status
("settled"), amount_usdc ("0.01"), network ("eip155:8453"), transaction (the
settlement transaction identifier) and payment_id (the receipt identifier).
The server also returns a PAYMENT-RESPONSE header. These payment metadata
are absent from a free preview. Preserve the actual receipt for reconciliation;
a documented schema alone is not evidence of a real settled transaction.
For local bookkeeping, use the Halte origin together with payment.payment_id
as the key to deduplicate stored settled receipts. Keep payment.network and
payment.transaction alongside it for chain reconciliation. session_id only
identifies ritual content and must not be used as a payment-receipt key.
These bookkeeping identifiers are not permission to reuse an authorization,
repeat a purchase, or automatically retry an uncertain settlement.

No private brief, credential or wallet key belongs in these query parameters.
These response-shape details do not prove that a payment has settled; use
payment confirmation and its durable receipt for that separate determination.

## Integration

Use same-origin relative routes above, or prepend the actual Halte deployment
origin. The human page offers a copyable command using its actual origin.
Machine-readable service description: /agent.json.

## This public deployment

Origin: https://api.halte-agent2026.workers.dev
No provider-specific routing header is required.
Handle PAYMENT-REQUIRED, PAYMENT-SIGNATURE and PAYMENT-RESPONSE with a compatible x402 v2 client.
The session price is 0.01 native USDC on Base mainnet (eip155:8453).
Never auto-retry an uncertain settlement or sign a second payment because a response was interrupted.
Keep the original request and receipt for reconciliation; do not automatically resubmit.
A payment authorization for another resource URL must not be reused for this origin.