Skip to main content
pay.sh is a registry, CLI, and MCP server for paid APIs. Syntalic is listed in the pay.sh registry, so an agent wired to pay.sh can discover and call our endpoints with no extra config. The pay CLI answers the 402 challenge and signs the payment from a local wallet. pay signs payments on Solana. With Syntalic it pays over x402 in USDC on Solana, so fund your pay wallet with USDC on Solana.
pay.sh’s registry listing can lag the live API. It currently lists a subset of the Shopper, Marketing and Analyst endpoints, not the measures, social or ontology routes, and still includes the inflation endpoint, which is currently unavailable. The live OpenAPI specification lists every route and price.

1. Install the pay CLI

On macOS:
Elsewhere:
Check the install with pay --version.

2. Set up a wallet

pay setup creates your wallet and protects it with Touch ID on macOS, Windows Hello on Windows, GNOME Keyring on Linux, or 1Password. Fund it with USDC on Solana before calling Syntalic; see pay.sh’s docs for funding options.
pay --sandbox runs with a test wallet. It is useful for trying pay’s discovery tools, but it can’t pay Syntalic: our API accepts only real USDC.

3. Launch an agent with Pay MCP attached

This injects the Pay MCP server and payment-safety instructions into the agent session. The agent can now discover paid providers, inspect their endpoints, and make wallet-approved calls.

4. Have the agent discover and call Syntalic

Inside the agent session, the typical tool flow is:
The agent searches the registry for “syntalic” or your use case, fetches the exact endpoint URL from get_skill_endpoints, and curls it. pay asks you to approve the payment in your wallet, then signs it and retries the call.
Always use the endpoint URL returned by get_skill_endpoints rather than constructing one. Check the registry against Syntalic’s live OpenAPI specification for current route availability and prices.

Manual MCP config

If you’d rather not launch your agent through pay claude, add Pay as an MCP server yourself. For Claude Code:
For Cursor (~/.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json) or another client, add this to its MCP configuration:

What happens behind the scenes

  1. The agent calls search_skills (a Pay MCP tool) and finds Syntalic in the registry.
  2. It calls get_skill_endpoints to get the exact URL for the call it wants, for example /v1/shopper/best-price.
  3. It issues a curl against that URL.
  4. The Syntalic API returns 402 Payment Required with the price and payment options.
  5. pay asks you to approve the payment, then signs an x402 payment in USDC on Solana with your local wallet.
  6. The retried request returns the paid response.
You don’t manage signing keys directly; pay does. See x402 for the underlying protocol.

Next steps

pay.sh agent quickstart

The official pay.sh walkthrough for launching Claude or Codex with Pay MCP.

Pricing

What each endpoint costs.