> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Start with the plan page, https://docs.scrip.dev/agents.md. It covers connecting, configuring, integrating, verifying, and operating a Scrip program.
> Events are asynchronous. `POST /v1/events` returns 202 when the event is accepted. Rules run afterward, so wait for the `event.completed` webhook or poll `GET /v1/events/{id}` before you read balances.
> Send the participant's `external_id` with an event. The first event for a new `external_id` enrolls the participant, so do not create participants first.
> The hosted MCP server is https://mcp.scrip.dev/mcp. It uses OAuth and is read-only. Make changes through the REST API or the dashboard.
> Add `.md` to any docs URL to get the page as Markdown. Request and response schemas are in https://docs.scrip.dev/openapi.json.

# Versioning

> How Scrip versions the API and announces breaking changes

Scrip has one live API version. Its base URL is `https://api.scrip.dev/v1`, and there is no version header to send.

Breaking changes are announced with a date in the [changelog](/changelog). A change that adds a field, an endpoint, or an error code is not breaking. Ignore fields you do not recognize.

## Webhook payloads

Webhook payloads carry `api_version`, the date of the payload contract the `data` object follows. A change that renames, removes, or retypes a payload field gets a new date. Scrip fixes the value when it creates the event, so a retried delivery keeps its original date. See [Webhooks](/guides/webhooks#versioning).

## Follow changes

Subscribe to the changelog feed at `https://docs.scrip.dev/changelog/rss.xml`. The [OpenAPI spec](https://docs.scrip.dev/openapi.json) always describes the live API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.