Building with LLMs

If you’re integrating ElasticPay with an AI coding assistant or agent, the documentation is available in machine-friendly formats. Point your tool at these instead of scraping HTML.

Resources

Resource	URL	Use for
Agent index	/llms.txt	Entry point: what exists, how to fetch it, and integration rules agents must follow
Full docs, one file	/llms-full.txt	Loading the complete documentation into a large context window
Compact docs	/llms-small.txt	Smaller context windows — integration content only
Any page as Markdown	append .md to its URL	Fetching a single page without HTML, e.g. /api/guides/test-clocks.md
OpenAPI schema	api.elasticpay.co/openapi.json	Exact request/response shapes — prefer this over prose for code generation
MCP server	https://mcp.elasticpay.co/mcp/sandbox	Tools, not text: search docs, read the schema, and run a full sandbox integration — see below

The MCP server

Reading is half the job; the ElasticPay MCP server is how an agent acts. It exposes the documentation and OpenAPI schema as tools with no authentication at https://mcp.elasticpay.co/mcp/docs, and — once connected via browser OAuth or a sk_sandbox_ key — the full sandbox integration surface: customers, saved payment methods (via fixture tokens), payments, refunds, recurring plans, test clocks, and the webhook event feed.

That last combination matters: with test clocks under tool control, an agent can build a recurring-billing integration and then watch it renew in simulated time, verifying its own work end to end — the integration loop walks through it. The complete surface is in the tool reference.

Suggested workflow

1. Give your agent https://docs.elasticpay.co/llms.txt — it includes instructions covering the constraints that matter most (supported payment methods, tokenisation rules, sandbox keys, webhook semantics).
2. For endpoint-level work, have it fetch the OpenAPI schema rather than relying on remembered API shapes.
3. If you have no sandbox key yet, hand the human https://www.elasticpay.co/agents and ask for the sk_sandbox_ key back — an agent cannot create an ElasticPay account itself. See Get a sandbox API key.
4. Develop against sandbox keys and verify time-dependent flows with test clocks — an agent can watch a payment plan renew in seconds instead of waiting a month.

Caution

Never let an agent handle raw card numbers or CVV — card capture goes through the widget or hosted payment page only, and server-side code handles pm_... tokens exclusively. This applies to generated code too.