# PairRail

> Make your pricing quotable by AI agents. One governed catalog every buyer agent can quote from. Deterministic prices, per-agent spend and access limits, and human approval above your thresholds, without changing your billing.

PairRail Atlas is seller-side pricing infrastructure. It turns a seller's pricing page, price book or Stripe/Chargebee products into governed, versioned rules and serves them to buyer agents. PairRail publishes prices and approval rules; payments keep running through the seller's existing billing.

## How it works

1. Import: a pricing page, spreadsheet, PDF or Stripe/Chargebee products become a catalog draft. Conflicts are flagged; nothing publishes on its own.
2. Publish: one versioned catalog goes to every protocol the seller's plan unlocks.
3. Quote: agents get deterministic quotes with price bounds, the rule applied and the catalog version. AI helps build the draft; it never sets a price.
4. Approve: above the seller's threshold, a person on the seller's team approves. Quotes are always indicative and non-binding; the seller's billing system creates the order.
5. Hand off: Atlas sends the approved quote to Stripe, Chargebee or any billing system via signed webhook (https://www.pairrail.com/docs/billing). The seller's processor charges the buyer. HubSpot gets quote writeback; Salesforce is next.

Example: A100 80GB at 500 hrs × $1.89 = $945.00, reserved commitment −10% = −$94.50, egress 2 TB × $0.05/GB = $100.00. Total $950.50, price bounds $930.00 to $960.00, rule tier.verified / volume ≥ 400 hrs, catalog v42. Below the seller's $5,000 threshold; above it, a person approves first.

## Protocols

One catalog, served on MCP, UCP, ACP, A2A and UAP (Sandbox: MCP only, with quotes marked as a rehearsal). AP2, MPP and x402 are on the roadmap; PairRail does not advertise a payable x402 route. Inspect live endpoints: https://www.pairrail.com/protocols
Product and protocol changes, newest first: https://www.pairrail.com/changelog (RSS: https://www.pairrail.com/changelog.xml, JSON Feed: https://www.pairrail.com/changelog.json)

## For agents

- Docs: https://www.pairrail.com/docs (API reference: https://www.pairrail.com/docs/api)
- OpenAPI spec: https://www.pairrail.com/openapi.yaml
- Everything in one file (this summary, every plan feature, every FAQ answer): https://www.pairrail.com/llms-full.txt
- MCP endpoint: POST https://www.pairrail.com/mcp?sellerId={sellerId} (JSON-RPC 2.0)
- Public catalog: GET https://www.pairrail.com/v1/public/catalog?sellerId={sellerId}
- Browsing, search and indicative pricing need no credentials. Quotes need a key the seller approved (POST /v1/access-requests, then poll with the pickup token).
- Every answer says indicative, approval-required or denied, with reasons and next actions. An approval-required quote reaches the seller's deal desk only when the buyer agent submits it (POST /v1/quote-requests/{id}/submit or MCP quote_submit), so submit only quotes the buyer wants at that price. The seller's approval caps are never in a response. A key's recent quotes that went through without approval count together toward the seller's limit, so splitting an order still routes it to approval.
- Quotes carry an EdDSA JWS over the priced facts (binding:false is inside it). Verify with https://www.pairrail.com/.well-known/jwks.json, or POST {"token": "<jws>"} to https://www.pairrail.com/v1/public/quote-verify. Sellers can export a signed evidence bundle per quote (policy decision, approvals, mandate, outcomes, audit events); the same endpoint checks it. Format spec and JSON Schema: https://www.pairrail.com/docs/quotes
- Each key has its own limits (quotes and pricing calls per hour, executes per hour, optional daily totals, optional keyed calls per month). Over a limit returns 429 VELOCITY_LIMIT; honor Retry-After.
- Delegating to other agents? Send agentPublicKey (a public JWK only your agent holds) with the access request: the issued key and anything bought are then delivered as a JWE encrypted to it, so relaying agents cannot read them. Mandates can name their holder with azp (your cred_… buyer key id) or, when signed by a seller-registered issuer, cnf.jkt (agent key thumbprint).

## Pricing (self-serve)

- Sandbox: $0. 1 catalog live on MCP for discovery and indicative pricing, 1,000 queries a month (hard cap), Sandbox trust badge (same checks as Agent-Ready; live prices, test quotes), 3 Deep verification runs a month, quotes and billing handoff as a marked rehearsal (Mock mode).
- Pro: $99/month, or $79/month billed yearly ($948/year). Billed in USD in every country.
- Pro includes 25,000 queries a month, then $2 per 1,000. No per-transaction take rate.
- Enterprise: custom contract. Signed DPA and questionnaires on request. SSO, residency and SLA terms are scoped in the order form. Includes a private Slack or Google Chat channel with our team.
- Support: email support@pairrail.com on every plan, Monday to Friday 09:00 to 18:00 IST, reply within one business day. Pro also gets a private Google Chat space with our team.
- Source of truth: https://www.pairrail.com/pricing (as Markdown: https://www.pairrail.com/pricing.md)

## Trust

- Security (agent limits, exact prices, data and keys): https://www.pairrail.com/security
- Disclosure policy: https://www.pairrail.com/legal/security
- Subprocessors: https://www.pairrail.com/legal/subprocessors
- Data processing terms: https://www.pairrail.com/legal/dpa
- support@pairrail.com · security@pairrail.com

## Links

- Product: https://www.pairrail.com/product
- Score your pricing, free: https://www.pairrail.com/score
- Interactive example: https://www.pairrail.com/demo
- Verify a seller's badge: https://www.pairrail.com/verify
- Market shift: https://www.pairrail.com/market-shift
- FAQ: https://www.pairrail.com/faq
- Support: https://www.pairrail.com/support
- About: https://www.pairrail.com/about
- Careers: https://www.pairrail.com/careers

---

Everything below is the full text of https://www.pairrail.com/pricing.md and https://www.pairrail.com/faq.

## PairRail Atlas pricing

> Start free in Sandbox. Go live on Pro when agents start asking you for quotes. Enterprise when you need contract terms. For how PairRail Atlas works day to day, see the [product walkthrough](https://www.pairrail.com/product).

Prices in USD, billed in USD in every country. Every tier includes everything in the tier before it. Source: https://www.pairrail.com/pricing (this file is written from the same plan list).

### Sandbox: $0

Live public pricing, free.

- 1 live catalog, 1,000 queries a month (hard cap)
- Live on MCP: agents discover your offers and get indicative prices
- Sandbox trust badge and public verify page, on the same checks as Agent-Ready
- 3 Deep verification runs a month: every price checked against your source*
- Agent readiness score and pricing lab preview
- Quotes and billing handoff run as a marked rehearsal, with mock billing and no live payment rails
- 1 seat, 14-day activity log
- 1 internal machine key for firm quotes and approved handoffs, plus up to 10 approved buyer-agent keys (discovery and indicative pricing stay public)
- Quick scan + limited personal AI extraction allowance*
- Vertical onboarding templates (AI inference, DevTools)
- Email support
- Sign in with Google, GitHub or a one-time email code

\* Sandbox includes a limited personal AI extraction allowance, and Deep verification runs draw on it. Advanced models and the catalog copilot require Pro.

Get started free: https://www.pairrail.com/onboard

### Pro: $99/month, or $79/month billed yearly ($948/year)

Live catalogs on all protocol rails.

Everything in Sandbox, plus:

- Live catalogs on MCP, UCP, ACP, A2A and UAP
- 25,000 queries a month, then $2 per 1,000
- 5 seats, 5 machine keys, 250 buyer-agent keys
- Approved quotes to Stripe, Chargebee or any billing system via webhook
- Quotes that can't be checked go to a person
- No cut-off: overage is billed at the end of the cycle
- Pull prices from Stripe or Chargebee into a draft you publish
- Expiry, rotation and revocation on every key
- Owner, Publisher, Editor, and Viewer roles
- Live quotes and billing handoff, with no Sandbox marking
- Agent-Ready badge in place of the Sandbox badge
- HubSpot writeback and eligibility
- 100 Deep verification runs/month: every price checked against your source†
- Catalog copilot: sync with your pricing page, fix conflicts, edit in plain language
- Pricing lab for tiers, commitments, and quote previews
- 90-day audit trail and catalog version history
- No per-transaction take rate
- Email support on business days
- Private Google Chat space with our team

† Pro includes 100 Deep verification runs a month as a soft allowance; a copilot sync with your pricing page uses one. Contact support if you need more capacity before the monthly reset.

Go live on Pro: https://www.pairrail.com/pricing

### Enterprise: Custom

Contract pricing, custom volume, signed paper.

Everything in Pro, plus:

- Custom volume, 50 seats, 2,500 buyer-agent keys and a 2-year audit trail
- Multi-approver deal desk: two or more people sign off on your largest quotes
- Contract prices per buyer, honored inside your price floors
- Every audit event streamed to your SIEM as a signed webhook
- MSA, signed DPA and Net-30 invoicing
- 1,000 Deep verification runs/month
- Export every catalog AI action as JSON
- 50 internal machine keys, with expiry, rotation and revocation
- Audit trail keeps your most recent 1,000 events, for up to 2 years
- Security questionnaire support
- Invoices payable by wire
- Priority P1 email when a live catalog or billing handoff breaks
- Private Slack or Google Chat channel with our team

SSO, residency, and SLA terms are scoped in your order form.

Email us about Enterprise: support@pairrail.com

### Plans, queries and billing

#### What’s included in Sandbox vs Pro?

The cards above are the full list. Sandbox is free: your public pricing is live on MCP with a hard query cap, and quotes run as a marked rehearsal. Pro is the live commerce plan: all five protocols, live quotes and billing handoff, included volume with overage, and the seats and keys on the Pro card.

#### What counts as a query?

Agents can find you for free; only real work counts against your quota:

- **Browsing is free.** `catalog_browse` and REST `/v1/public/catalog` are edge-cached and never use your query quota. Crawlers and agents exploring your products never cost you credits.
- **Compute counts.** `catalog_discover`, `pricing_calculate`, `readiness_inspect` and authenticated agent operations count toward your plan’s included monthly volume, and only when they succeed. Access requests, failed calls and retries that replay an earlier quote are free.
- **Protocol overhead never counts.** MCP handshakes (`initialize`, `tools/list`, `tools/listChanged`, `ping`), static discovery files (`/llms.txt`, `/.well-known/*`, `/openapi.yaml`) and health probes never use quota.

Sandbox traffic (1,000/month, hard-capped) is metered separately and does not use Pro included volume after you upgrade.

#### How does overage work on Pro?

Pro includes 25,000 queries per month. After that, overage is $2 per 1,000 queries ($0.002 per query), billed through our payment partner at the end of your billing cycle.

Unauthenticated public traffic never creates overage and does not use your included queries. It has its own monthly allowance of the same size; once that is used, anonymous calls pause with a 429 response. Only agents with a validated machine key use your included queries and overage capacity.

#### Can I pause agent traffic or turn off anonymous pricing?

Yes, on every plan. Your workspace has a seller kill switch that pauses all agent traffic (public and keyed) immediately, a toggle for anonymous pricing, an optional daily anonymous query cap, and per-buyer key expiry. Every kill-switch change is recorded in your audit log.

#### Can I see a breakdown of my query usage by type?

Yes. Your workspace billing panel shows queries grouped by category: *Catalog Browse*, *Catalog Discover*, *Indicative Pricing*, *Readiness*, *Access Requests* and *Agent (authenticated)*. You see which operation type is driving volume before you reach overage, so there are no surprises at billing time.

#### Do I need a credit card for Sandbox?

No. Sign in with Google, GitHub or a 6-digit email code to get an isolated Sandbox workspace and start extracting and scoring readiness without a card. You only pay when you upgrade to Pro.

#### Can I switch between monthly and yearly?

Yes. Choose monthly or yearly at checkout. To switch later, use the Subscription panel in your workspace. It shows what you will pay before you confirm.

- **Monthly to yearly** takes effect right away. You pay the yearly price minus a credit for the unused part of your current month, and your yearly term starts that day.
- **Yearly to monthly** takes effect at the end of your paid year. Nothing is charged until then, and there is no partial refund for the rest of the year. You can undo it before that date.

Switching is not available during a free period or while renewal is cancelled. For help, email [support@pairrail.com](mailto:support@pairrail.com?subject=PairRail%20Pro%20billing%20interval).

#### Who processes payment for my subscription, and can I cancel?

Checkout and subscription billing for your Atlas plan run through our payment partner. You can manage or cancel the subscription from the billing portal linked to your account, or email [support@pairrail.com](mailto:support@pairrail.com).

#### Who bills my customers?

You do, through your existing billing, and tax filing stays with you. PairRail takes no per-transaction cut. [How the handoff works](https://www.pairrail.com/product#connect-stack).

#### Is Enterprise self-serve?

No. Enterprise is contract paper: custom volume, a signed DPA on request, and questionnaires. SSO, residency and SLA terms are scoped in your order form. Sandbox and Pro use Google, GitHub or email OTP. Email [support@pairrail.com](mailto:support@pairrail.com).

## FAQ

### Getting started

#### How do I start using Atlas?

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](https://www.pairrail.com/score) or go straight to [Onboard](https://www.pairrail.com/onboard) or your [workspace](https://www.pairrail.com/workspace). Enterprise SSO (SAML / OIDC) is scoped in the Enterprise order form, and is not required for Sandbox or Pro.

#### What should I paste or upload first?

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.

#### How do I know if my catalog is ready for agents?

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.

#### What happens when I publish?

Publishing versions your approved commercial truth and projects it onto the protocol rails your plan allows (see [which protocols](https://www.pairrail.com/faq#q-which-protocols-does-atlas-support)). Agents only see the version you publish.

#### Can I use Atlas before any agents call me?

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

#### Do I need to change my billing, CRM or ERP?

No. You keep your existing stack. On Pro, connect Stripe or Chargebee in Integrations, or any other system through the signed webhook; [what happens after approval](https://www.pairrail.com/faq#q-what-happens-after-a-quote-is-approved) is below. 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. Stripe connections accept only restricted (`rk_`) keys. Tax and fulfillment stay with your existing providers. Enterprise can honor signed contract pricing.

#### What happens after a quote is approved?

Atlas sends the approved quote to your billing system (Stripe, Chargebee or any billing system via signed webhook). Your processor charges the buyer, exactly as it does today. Above your threshold, a person on your team approves the quote first. Below it, the quote only goes to your billing when the buyer’s own human has authorized payment, and only if you gave that buyer’s key the `quote:execute` scope, which is off by default. Atlas refuses payment authorizations that are expired or capped below the quote total, and enforces each key’s hourly and daily handoff limits. If you register your issuers’ public keys (ES256, RS256 or EdDSA), Atlas also verifies each authorization’s signature, requires an expiry, amount cap and unique ID, and stops one authorization covering two quotes; you can require signed authorizations for every handoff. Your processor stays the authority on the payment. Sandbox uses Mock mode so you can rehearse the handoff without live charges.

### Product

#### What is PairRail Atlas?

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.

#### Who is Atlas for?

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.

#### What does “agent-ready” mean here?

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.

#### What is Verified Agent-Ready?

A PairRail badge for catalogs that are published, score 85 or higher, and have no publication blockers. Pro and Enterprise catalogs earn it. A Sandbox catalog that passes the same checks gets the Sandbox badge instead. Agents get its live prices, but its quotes are tests that never reach live billing. If you pause the live catalog, the public badge switches to Paused until you publish again. Check any seller on [Verify](https://www.pairrail.com/verify). It is not a third-party certification.

#### Do agents bind my company when they get a quote?

No. Quotes stay indicative until they are approved and handed off to your own billing. Atlas publishes your quote authority (that quotes are indicative and nothing binds before that handoff) on UCP and in quote envelopes.

#### How do I set what an agent can quote without a human?

In the workspace, set the quote cap agents can work within, the cap above which a manager approves, and your discount fences. Save them to the catalog draft and publish. Per-key limits apply on top, without republishing; see [agent access](https://www.pairrail.com/faq#q-how-do-scoped-agent-credentials-and-velocity-controls-protec).

#### What do agents see about my approval rules?

Only the outcome. Each pricing answer or quote tells the agent whether it is indicative, needs approval or is denied, the reasons, who must approve and what it can do next. Your autonomous cap, manager cap and automatic discount limit are never in an agent response, on REST or any protocol rail.

#### Can an agent get around my approval limit by splitting an order?

No. Quotes an agent key got without approval count together toward your autonomous cap over a rolling window, 24 hours by default. Once the combined total crosses the cap, the next quote goes to your deal desk like one large order would. Only that key’s auto-approved quotes in the same currency count; quotes a person approved, and revoked or expired quotes, do not. Change the window in the workspace under *Human-approval tiers*, or set it to 0 to turn the check off.

#### What is the deal desk?

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 can require two or more different approvers on quotes above your manager max.

#### What is Atlas Insights and how does it differ from Quota?

**Plan Quota** meters raw computational queries consumed against your monthly allowance (e.g. 25,000 queries on Pro across catalog discovery, price calculation, and readiness inspections). **Atlas Insights** puts that usage in commercial context: metered agent queries by type, recorded agent events by protocol rail when available, how many offers are gated from anonymous agents by disclosure level, agent searches that matched no public offer, and quotes waiting on or resolved by your deal desk. Insights only shows what was recorded. It never fills gaps with estimated or sample traffic.

#### Does PairRail process payments?

No. PairRail is never the merchant of record and never handles money. Buyer agents get quotes and approval rules from us; payment happens through your existing billing.

### Plans & billing

#### What’s the difference between Sandbox and Pro?

Sandbox is free: one catalog live on MCP for discovery and indicative pricing, a Sandbox trust badge on the same checks, 3 Deep verification runs a month, quotes and billing handoff as a marked rehearsal with Mock mode, and a hard 1,000 queries/month cap. Pro unlocks production protocol rails, hands approved quotes to your own payment rails or a signed webhook, includes 25,000 queries/month, and keeps serving agents with soft overage instead of a hard cut.

#### How much is Pro?

Pro is $99/month, or $79/month when billed yearly ($948/year), billed in USD. Overage is $2 per 1,000 queries after the included volume. Choose monthly or yearly on the [pricing page](https://www.pairrail.com/pricing) before checkout.

#### Can I switch between monthly and yearly later?

Yes. Choose monthly or yearly at checkout. To switch later, use the Subscription panel in your workspace. It shows what you will pay before you confirm.

- **Monthly to yearly** takes effect right away. You pay the yearly price minus a credit for the unused part of your current month, and your yearly term starts that day.
- **Yearly to monthly** takes effect at the end of your paid year. Nothing is charged until then, and there is no partial refund for the rest of the year. You can undo it before that date.

Switching is not available during a free period or while renewal is cancelled. For help, email [support@pairrail.com](mailto:support@pairrail.com?subject=PairRail%20Pro%20billing%20interval).

#### Who processes payment, and can I cancel?

Checkout for your PairRail subscription runs through our payment partner. 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.

#### How do I get support?

Every plan can email [support@pairrail.com](mailto:support@pairrail.com) or use the [support form](https://www.pairrail.com/support). We are available Monday through Friday, 09:00 to 18:00 IST, and reply within one business day. Pro also gets a private Google Chat space with our team; request it from the Subscription panel in your workspace. Enterprise gets a private Slack or Google Chat channel, with response times set in your order form.

#### Is Enterprise available self-serve?

No. Enterprise is a custom contract for volume, SLA and multi-workspace needs. SSO and data residency are not available today. If you need them, they are scoped in your order form. Use Email us about Enterprise on the [pricing page](https://www.pairrail.com/pricing) or email support@pairrail.com.

### Queries & overage

#### What counts as a query?

Agents can find you for free; only real work counts against your quota:

- **Discovery is free.** Basic catalog browsing (`catalog_browse` and `/v1/public/catalog`) is edge-cached and costs you nothing. Spiders and agents discovering your products never consume your quota.
- **Quota queries.** Dynamic search (`catalog_discover`), indicative pricing (`pricing_calculate`), readiness evaluations and authenticated agent operations count toward your plan's included quota, and only when they succeed.
- **Never counted.** Handshakes (`initialize`, `tools/list`, `ping`), static metadata, and health probes are permanently exempt. So are access requests (`request_catalog_access`), calls that fail, and retries that replay a quote you already have.

#### How does Pro overage work?

Pro includes 25,000 queries per month. Additional queries are billed at $2 per 1,000 queries ($0.002 per query) at billing cycle end.

Unauthenticated public calls never create overage charges and do not use your included 25,000 queries. They have their own monthly allowance of the same size; once it is used, anonymous traffic is paused with a 429. Only authenticated agents with approved machine keys use your included queries and overage capacity.

#### How does PairRail handle bots and traffic spikes without browser CAPTCHAs?

Autonomous AI agents, MCP clients, and LLM tool execution engines run in headless environments. They cannot click visual tiles or execute interactive browser scripts, so web CAPTCHAs would lock them out.

PairRail uses progressive access controls that work for machine clients:

- **Per-client limits:** unauthenticated pricing is limited to 30 requests per minute per client, with per-seller safeguards in each running instance. The hosting edge provides the global limit across instances.
- **Free static discovery:** Basic catalog browsing (`catalog_browse`) is edge-cached and unmetered to the seller.
- **Optional proof-of-work:** When a signing secret is configured and an anonymous compute client reaches its own limit, PairRail can return a scoped SHA-256 challenge. A solution never bypasses seller-wide or protected-route limits.
- **Access-request filtering:** Machine key requests validate contact-email syntax and block a maintained list of disposable domains. Seller approval is still required.
- **No overage from anonymous traffic:** public crawlers never create overage charges on your account.

#### What if I hit the Sandbox query cap?

Sandbox hard-caps at 1,000 queries/month. Upgrade to Pro to continue with 25,000 included queries plus soft overage for authenticated agents, or wait until the next monthly reset.

### Protocols & agents

#### How do agents reach my catalog?

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.

#### Do I need a custom domain or /.well-known on my site?

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.

#### Who can call my catalog?

Discovery and indicative pricing can stay public so agents find and price you. Creating a firm quote or handing an approved quote to your billing requires a seller-approved machine key. Approve an inbox request or issue a key in Agent gateway; the secret is shown once. Limits, rotation and revocation are under [agent access](https://www.pairrail.com/faq#q-how-do-scoped-agent-credentials-and-velocity-controls-protec).

#### How do I know which agent is asking for a quote?

Every quote shows the agent key that asked for it, which you issued or approved. If the agent also signs its request with Web Bot Auth, Atlas checks the signature against the keys that agent publishes and shows you who signed and whether it verified. Signatures are recorded, not required, so they never block a request.

#### Which protocols does Atlas support?

Sandbox serves MCP (plus REST `/v1`): discovery and indicative pricing are live, and quotes are marked as a Sandbox rehearsal. Pro and Enterprise unlock MCP, UCP, ACP, A2A and UAP with live quotes and no Sandbox marking. AP2, MPP and x402 remain on the roadmap. See [Protocols](https://www.pairrail.com/protocols).

#### What does the Sandbox marking on quotes mean?

On Sandbox, your catalog, discovery and indicative prices are live for agents. Quote and execute responses carry a Sandbox marking that says they are a rehearsal: the billing handoff runs only in Mock mode, never on your live billing. Move to Pro to send live quotes to your billing system.

#### Do I need a separate integration per protocol?

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

#### Can I inspect live endpoints before I subscribe?

Yes. The [Protocols](https://www.pairrail.com/protocols) page opens live inspector views for the five commerce rails (`/mcp`, `/.well-known/ucp`, `/protocols/acp`, `/a2a`, `/protocols/uap`). The UCP product feed is part of UCP, not a separate rail.

#### Is there an OpenAPI surface?

Yes, as **API documentation**, not a sixth protocol rail. See [/openapi.yaml](https://www.pairrail.com/openapi.yaml) for HTTP schemas used by the console and gateway. Commerce protocols remain MCP, UCP, ACP, A2A and UAP.

#### Does PairRail support x402 payments?

Not yet. x402, AP2 and MPP are on the [protocol roadmap](https://www.pairrail.com/protocols). PairRail can format x402 payment requirements from your published catalog in library code, but no payable x402 route is live, because payment verification and replay protection are not yet implemented and tested.

### Workspace & data

#### How does extract work?

Paste or upload pricing content. Atlas structures products and offers, flags conflicts, and scores readiness. Deep verification reads long or messy sources section by section, checks every price against the source text, accounts for every amount the source prints, and flags anything it cannot verify so it cannot be published unchecked. Sandbox includes a limited personal AI extraction allowance and 3 Deep verification runs a month. Pro includes 100 Deep verification runs per month, plus the catalog copilot: change the draft in plain language, get options to fix a conflict, or sync the catalog with your pricing page, with every change shown before it is applied. Enterprise starts from a higher contracted monthly Deep verification 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.

#### Can more than one person use my workspace?

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.

#### What is the difference between internal machine keys and buyer-agent keys?

Both are Bearer keys (`pat_…`) with the same scopes, limits, expiry, rotation and revocation. They differ in who they are for:

- **Internal machine keys** are for your own agents and tools, such as a deal-desk bot, your own MCP client, or scripts that test quotes. You issue them in Agent gateway with *Issue internal key* and copy the key yourself. They can be allowed to see internal-only offers, and they never expire unless you set a date. Sandbox includes 1, Pro includes 5.
- **Buyer-agent keys** are for one outside buyer's agent each, such as a customer's procurement agent or a partner platform. The agent asks for access, you approve it under Access requests, and the agent collects its key once with a pickup token. They never see internal-only offers, and revoking one cuts off only that buyer. They expire 90 days after approval unless you renew them, and keys with no use for 30 days are flagged so you can revoke them in one step. Sandbox includes 10, Pro includes 250, separate from internal keys. Expired and revoked keys free their slot.

Browsing and indicative pricing need no key at all. A key is needed for firm quotes, and sending quotes to your billing stays off until you turn it on for a key.

#### How do I limit, rotate or revoke an agent's access?

You approve which machines can act on your catalog. Every plan includes scoped credentials with expiry, rotation, revocation, and per-key quote limits, so you can cut or throttle access without republishing. Per key you can set scopes (browse and quote by default; sending approved quotes to your billing only when you add `quote:execute`), an expiry date, maximum quotes per hour, maximum pricing calls per hour, a daily quoted total, and hourly and daily limits on handoffs to your billing. Each approved buyer gets its own key, which does not count against your internal key limit (Sandbox: 10 buyer keys, Pro: 250). Identity signals an agent sends with its access request (such as Web Bot Auth or Visa TAP tokens) are shown as *claimed*, not verified, so you decide how much to trust them.

#### Can I keep some prices private or customer-only?

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.

#### Can I pause my live catalog?

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.

#### How long is audit history retained?

Sandbox keeps about 14 days of activity. Pro retains audit trail and catalog versions for 90 days. Audit history is kept separately for each seller (up to your most recent 1,000 audit events), so other sellers’ activity never pushes yours out. Enterprise can extend retention under contract.

### Security & trust

#### Where is PairRail hosted?

Core services run on Google Cloud in `us-central1` (Firebase Authentication and Hosting, Cloud Run, and model extraction). Cloudflare stores catalog and workspace state (R2 and D1) and handles DNS, CDN and edge telemetry. The full list is on [Subprocessors](https://www.pairrail.com/legal/subprocessors).

#### How are seller payment keys and processor secrets encrypted?

Stripe restricted keys, Chargebee API keys, webhook signing secrets and not-yet-claimed buyer agent keys are encrypted at rest with AES-256-GCM. Each value is bound to its organization or access request, so it cannot be decrypted in another tenant’s context. The encryption key is held in the runtime’s secret configuration, not in the data store, and the service refuses to store new secrets if no key is configured. Agent keys are stored only as SHA-256 hashes after the buyer picks them up. Atlas never stores customer payment card numbers. Customer-managed keys (Cloud KMS) are not available today. If an Enterprise contract needs them, they are scoped in your order form.

#### Who owns my catalog and pricing content?

You do. PairRail processes Customer Content only as needed to operate the service (hosting, protocol projection, extraction, backups). See the [Data Processing Terms](https://www.pairrail.com/legal/dpa) and the [Privacy Policy](https://www.pairrail.com/legal/privacy).

#### Do you sell or train on my price books?

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.

#### How do I report abuse or a security issue?

Email [security@pairrail.com](mailto:security@pairrail.com) with “Security disclosure” in the subject, or follow the [disclosure policy](https://www.pairrail.com/legal/security). How Atlas keeps agents inside your limits is on [Security](https://www.pairrail.com/security). [support@pairrail.com](mailto:support@pairrail.com) still reaches us. For product misuse, see the [Acceptable Use Policy](https://www.pairrail.com/legal/acceptable-use).

#### Do you have a DPA and a subprocessor list?

Yes. Public processor terms are on the [DPA](https://www.pairrail.com/legal/dpa) page. Providers are listed under [Subprocessors](https://www.pairrail.com/legal/subprocessors). Email [support@pairrail.com](mailto:support@pairrail.com) if you need a signed DPA on an order form.