Help someone find their route.
Search our public catalogue, estimate one print with delivery, then give the customer a link to review and personalise it.
These interfaces are free and read-only. They cannot take payment, place an order or access customer information. No API key is required.
1. Find a route
GET /api/agent-catalog?region=AU&q=marathon
Search by name, sport, city or country. Use AU for AUD and UK for GBP. Starting prices are A5 matte unframed, excluding shipping. Static snapshots: AU · UK.
2. Estimate the print
GET /api/agent-quote?route=london-marathon®ion=AU&country=AU&sizeKey=a3&paperKey=matte&frameKey=oak
The destination country is required. Quotes use the checkout pricing rules and cover one print. See the OpenAPI document for options and response fields. Unknown or duplicate parameters are rejected.
3. Hand over to the customer
Return customiseUrl. It sets the design options and currency. The customer reviews the design, adds it to their cart, chooses delivery and pays through Stripe. This is an estimate, not a reserved price; changes and additional items can change the total.
Product feed
If you ingest merchant catalogues, use the JSONL feeds rather than scraping: AU · UK. They follow the OpenAI/ACP product specification, one row per route and size, at the Museum Matte unframed price. enable_search is true and enable_checkout is false — we have not implemented ACP checkout endpoints, so the buyer finishes on apexprints.co. Feed prices are generated from the same tables the checkout charges from.
What to tell shoppers
- We sell made-to-order physical route prints, framed or unframed.
- Catalogue routes may be illustrative and may differ by race year. Use a GPX upload for the customer's exact activity.
- Don't promise a delivery date. Link to shipping and returns.
- Don't send GPX data, addresses or payment credentials to this discovery API.
On x402 and autonomous payment
We do not accept x402 payments and are not listed in its Bazaar. x402 settles stablecoin micropayments for machine-consumed resources such as API calls and data. An Apex print is a physical, made-to-order object that needs a human-approved design, a delivery address and a returns path, so the part an agent could pay for autonomously is the part we deliberately give away free.
The same reasoning applies to agent checkout generally: we publish an ACP-shaped product feed so assistants can find and price the prints, but the purchase itself stays with the customer. If we later add a paid digital product, or ACP checkout endpoints, it will be a separate integration with its own payment verification, fulfilment and refund handling, documented here.