Skip to content

Documentation / Get started

Get started

Start here

  1. Browse and price, no key. catalog_browse over MCP, or /v1/public/pricing/calculate over REST.
  2. Ask the seller for a key. Request access, a person approves, you claim the key once.
  3. Quote with the key. Send an Idempotency-Key; above the seller’s threshold a person approves.

Basics

  • Base URL: https://www.pairrail.com. All requests and responses are JSON over HTTPS.
  • Seller ID: a slug such as northstar-compute (the example seller in these docs), sent as ?sellerId= on public calls.
  • Public vs keyed: browsing, search and indicative pricing need no credentials. Quotes and execute need a seller-approved Bearer key (pat_…) that works only for that seller.
  • Nothing binds early: prices and quotes are indicative until approved, and the seller’s own billing runs the payment.
  • Plans: Sandbox sellers are served on MCP only: discovery and indicative pricing are live, and quote responses carry a Sandbox marking. Pro sellers are live on MCP, UCP, ACP, A2A and UAP.