feat(services): add Talarion

[avi-sundaresan]

Motivation

Talarion maintains a knowledge base of verified, dated assertions, each a Q/A pair returned only when the querying LLM would otherwise answer the underlying question incorrectly. POST /v1/search answers a question with those assertions and their source URLs; POST /v1/fetch returns the archived text of up to 20 URLs as of any date, which is what makes point-in-time work possible without lookahead.

It is distinct from the web-search services already listed: those retrieve live pages, while this returns dated, cited assertions, and its fetch endpoint answers "what did this page say on this date" from an archive.

• Service name: Talarion
• Live service URL: https://api.talarion.com
• Provider URL: https://talarion.com
• OpenAPI or API reference URL: https://api.talarion.com/openapi.json (reference: https://docs.talarion.com/search)

Summary

• The service is live and accepts MPP payments.
• This PR adds or updates its entry in schemas/services.ts.
• Listed endpoints, prices, and payment methods match the live service.
• Public documentation and icon URLs are stable and accessible.
• pnpm generate:discovery succeeds.
• pnpm check:types passes.
• pnpm build succeeds.

Key design considerations

• Integration: first-party. MPP is served natively on api.talarion.com, not through a proxy; realm matches the origin agents call.
• Payment methods and intents: tempo / charge, USDC.e on mainnet (chain 4217), via the hosted relay. POST /v1/search is a flat $0.002 per call ("2000"). POST /v1/fetch is dynamic: the challenge quotes $0.05 for each document that specific request will return, counted before any work runs, so a caller pays for exactly what comes back and a request we hold nothing for is answered free with no challenge at all.
• Provider relationship: We own and operate Talarion.
• Directory fit: Production service with existing paying subscription customers; MPP is an additional way to pay for the same two endpoints rather than a separate wrapper. Not a duplicate: no listed service returns dated, cited assertions, and none serves point-in-time archived page text.

Verification

Against the live origin:

$ curl -i -X POST https://api.talarion.com/v1/search \
    -H 'Content-Type: application/json' -d '{"query":"test"}'
HTTP/2 402
www-authenticate: Payment id="...", realm="api.talarion.com", method="tempo",
  intent="charge", request="...", header="Payment-Authorization"

POST /v1/fetch for one archived URL quotes "amount": "50000" (= $0.05, 6 decimals) against currency 0x20C000000000000000000000b9537d11c60E8b50 on chainId 4217, recipient 0x06F4AE29dbefe6e3154cB810bEE2BA930aE78419 — matching the TEMPO_PAYMENT defaults and the amounts declared in this entry.

Discovery: https://api.talarion.com/openapi.json is served same-origin with a 200 and carries x-payment-info (price + protocols) on both paid operations.

In this repo, on Node 24:

• pnpm vitest run schemas/services.test.ts — 9441 passed
• pnpm check:types — clean
• pnpm generate:discovery — 143 services, 1458 endpoints
• pnpm build — exit 0, with dist/public/icons/talarion.svg shipped

The entry is appended to the end of the services array rather than inserted alphabetically, matching the convention the file has followed since roughly its 97th entry.

[vercel]

@avi-sundaresan is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🔀 Changed Services

✅ Added

• talarion

[github-actions]

Thanks for submitting a service to the MPP directory!

Complete the service pull request template in your PR description before review. It contains the current submission requirements and review criteria.

Service submission guide