Frequently asked questions

Sign in with Google, GitHub, or a 6-digit email code (no passwords). We create an isolated Sandbox workspace and catalog for you. No card required. Then paste a price book on Score or go straight to Onboard / your workspace.

A real price book or packaging sheet: product names, SKUs if you have them, list prices, currencies, billing periods, and any seat or region rules. Messy text is fine. Atlas structures offers and flags conflicts before you publish.

Use the readiness score in the workspace. It highlights missing prices, conflicting offers, weak packaging, missing quote authority, and other blockers. Raise the score, then publish when the catalog is good enough for agents to trust.

Publishing versions your approved commercial truth and projects it onto the protocol rails your plan allows. Sandbox stays watermarked and MCP-only. Pro serves live catalogs on all rails without the sandbox watermark.

Yes. Most sellers extract, score, and publish first, then connect agent traffic later. Sandbox is built for that dry run.

No rebuild required. On Pro, connect Stripe, Dodo, or a signed ERP/OMS webhook in Governance → Connect stack. Import Stripe or Chargebee products into a catalog draft (you still publish). Save a HubSpot private app token to write quotes as deals and access or deal-desk items as tasks, and to read six eligibility fields. Salesforce is next; join the waitlist in the workspace. You stay merchant of record; PairRail does not hold customer funds or file tax on your behalf.

After an approved quote, a buyer agent calls execute with a delegated payment token. On Pro, Atlas charges through your connected merchant credentials on your payment rails, or emits a signed webhook to your ERP. Sandbox uses Mock mode so you can rehearse settle → fulfill without live charges. Your billing stack does not need agentic AI, only the same APIs it already uses for web checkout. Fulfillment credentials return to the agent in the protocol response envelope.

Atlas holds your approved pricing, packaging, and policy in a versioned, evidenced catalog. Agents read that catalog on the rails that exist today. Adapters can change as protocols version. The catalog does not.

API-first and AI-native product teams, and developer-tool vendors who need catalogs agents can discover and price without scraping PDFs or guessing list prices. Marketplace operators, distributors, and broader quote-led B2B software are on the rail next.

Your commercial truth is structured, versioned, readiness-scored, and served on protocol rails agents can consume without one-off integrations, including a published quote mandate. Pro adds evidence-linked provenance and production rails. A catalog is agent-ready when its readiness score is 85 or higher.

A PairRail badge for Pro catalogs that are published, score 85 or higher, and have no publication blockers. If you pause the live catalog, the public badge switches to Paused until you publish again. Check any seller on Verify. It is not a third-party certification.

No. Quotes stay indicative until execute on your connected billing rails. Atlas publishes your quote authority (caps, discount fences, and that nothing binds until execute) on UCP and in quote envelopes. Out-of-policy asks escalate to deal desk instead of inventing a number. PairRail is not merchant of record for your buyers.

In the workspace, set autonomous and manager quote caps plus discount fences, then save them to the catalog draft and publish. Agents read that profile with the catalog. On each machine key, you can also cap quotes per hour and spend per day. Those key limits apply without republishing.

Fail-closed exception handling. When a request exceeds the authority you published, Atlas returns a coded error (revise, poll for approval, or back off) and queues the ask for a human instead of guessing. Pro includes the deal-desk queue; Enterprise adds multi-approver workflows.

No. You keep your existing stack. Live today: Stripe/Dodo settlement, signed webhook handoff, Stripe or Chargebee catalog pull into a draft, and HubSpot writeback plus eligibility. Salesforce is next. Enterprise can honor signed contract pricing.

Sandbox is free for validation: one sandbox catalog, MCP only, watermarked responses, mock settlement rehearsal, and a hard 1,000 queries/month cap. Pro publishes up to three live catalogs, unlocks production protocol rails, live settlement on your payment rails or webhook handoff, includes 25,000 queries/month, and keeps serving agents with soft overage instead of a hard cut.

Pro is $59/month, or $49/month when billed yearly ($588/year), billed in USD. Overage is $2 per 1,000 queries after the included volume. Choose monthly or yearly on the pricing page before checkout.

No. Sign in and start extracting and scoring without a card. You only pay when you upgrade to Pro.

Choose monthly or yearly before checkout. After you subscribe, email support@pairrail.com and we will move the subscription. There is no self-serve interval switch.

Checkout runs through our payment partner (Dodo Payments). PairRail does not store full card details. You can manage or cancel in the billing portal linked to your account, or email support@pairrail.com.

No. Enterprise covers custom volume, SLA, SSO, residency, and multi-workspace needs under contract. Use Email us about Enterprise on the pricing page or email support@pairrail.com.

Each public or authenticated catalog, discover, indicative pricing, readiness, MCP tool, or protocol commerce call against your seller catalogs typically counts as one query. Public discovery and pricing count toward Sandbox’s 1,000/month hard cap. Sandbox traffic does not consume Pro included volume after you upgrade.

After 25,000 queries in a month, overage is $2 per 1,000 queries. Pro keeps serving agents; usage continues and overage bills through our payment partner.

Sandbox hard-caps at 1,000 queries/month. Upgrade to Pro to continue with included volume plus overage, or wait until the next month resets.

After you publish, open Agent gateway → Protocol rails and copy the MCP (and catalog) URLs. Those PairRail URLs include your sellerId, which is how Atlas routes agents to your workspace today. Paste the MCP URL into Claude, Cursor, or any MCP client. Custom domains on your own site are not required for Sandbox or Pro.

No for the working loop. Share stamped PairRail URLs from Protocol rails. If a crawler must hit yoursite.com/.well-known/ucp (RFC 8615 / Google UCP), open the same panel and copy the optional Next.js or Cloudflare Worker rewrite snippet, which proxies your apex to PairRail. PairRail does not manage your DNS or verify that proxy. Managed custom domains for protocol endpoints are an Enterprise option scoped per contract, not self-serve on Sandbox or Pro.

Discovery and indicative pricing can stay public so agents find and price you. Creating a binding quote or executing payment requires a seller-approved machine key. Approve an inbox request or issue a key in Agent gateway; the secret is shown once. Set quote and spend velocity on that key, then rotate or revoke anytime without republishing the catalog.

Sandbox exposes MCP with watermarked responses (plus authenticated REST /v1). Pro and Enterprise unlock UCP, MCP, A2A, UAP, and ACP production endpoints without the sandbox watermark. Settlement rehearsal on Sandbox uses Mock; live payment rails are Pro. Signed AP2 interop is next, so execute can verify a payment mandate and settle on your rails. MPP and x402 follow on that path. See Protocols.

It marks responses as non-production. Agents can probe your catalog, but the surface is clearly sandbox and should not be treated as live commercial truth.

No. Publish commercial truth once in Atlas. Protocol projections come from that catalog, so you are not maintaining a price book per rail.

Yes. Homepage protocol chips and the Protocols page open live inspector views for the five commerce rails (/.well-known/ucp, /mcp, /a2a, /protocols/uap, /protocols/acp). The UCP product feed is part of UCP, not a separate rail.

Yes, as API documentation, not a sixth protocol rail. See /openapi.yaml for HTTP schemas used by the console and gateway. Commerce protocols remain UCP, MCP, A2A, UAP, and ACP.

Sign in with Google, GitHub, or a one-time email code. First login provisions an isolated org and a Sandbox catalog so you can extract, score, and publish without a credit card. Enterprise SSO (SAML / OIDC) is scoped in the Enterprise order form, and is not required for Sandbox or Pro.

Paste or upload pricing content. Atlas structures products and offers, flags conflicts, and scores readiness. When a sheet is ambiguous, Pro can run Agentic verification to reconcile conflicting prices with deterministic tooling. Sandbox includes a limited personal AI extraction allowance for exploration. Pro includes 100 Agentic multi-pass extracts per month with evidence-linked provenance, plus catalog AI copilots (remediation, NL drafts, publish QA, change-risk). Enterprise starts from a higher contracted monthly Agentic extract allowance (1,000/mo in the base Enterprise ladder) and can raise volume further under the order form, with custom extract prompts and SIEM-exportable AI audit trails.

Sandbox is one seat. Pro includes 5 seats on the same seller workspace. The owner assigns each teammate a role: Owner, Publisher, Editor, or Viewer. Editors can draft and extract. Publishers can publish, pause live catalogs, and manage machine keys. Only the Owner invites people and manages billing. Enterprise adds multi-workspace and SSO role mapping under contract.

Yes. You approve which machines can act on your catalog. Pro includes scoped credentials with rotation, revocation, and per-key quote or spend limits, so you can cut or throttle access without republishing.

Yes. Each offer has a disclosure setting: public, customer, or private. Public catalog, discover, and indicative pricing surfaces only show offers marked public. Customer offers stay gated for eligible buyers; private offers stay off public rails.

Yes. Publishers and Owners can pause a live catalog. That clears the live published pointer, keeps version history, and moves the Verified Agent-Ready mark to a paused state until you resume. Agents stop seeing a live catalog while paused.

Sandbox keeps about 14 days of activity. Pro retains audit trail and catalog versions for 90 days. Enterprise can extend retention under contract.

Core services run on Google Cloud in us-central1 (Firebase Authentication and Hosting, Cloud Run, Cloud Storage, and model extraction). Cloudflare handles DNS, CDN, and optional edge telemetry. The full list is on Subprocessors.

You do. PairRail processes Customer Content only as needed to operate the service (hosting, protocol projection, extraction, backups). See the Data Processing Terms and the Privacy Policy.

We do not sell Customer Content. Extraction uses configured model providers to transform content you submit for your workspace. Privacy explains how that processing works.

Email security@pairrail.com with “Security disclosure” in the subject, or follow the Security page. support@pairrail.com still reaches us. For product misuse, see the Acceptable Use Policy.

Yes. Public processor terms are on the DPA page. Providers are listed under Subprocessors. Email support@pairrail.com if you need a signed DPA on an order form.