Skip to content

Product

One approved catalog every buyer agent can read and quote from.

PairRail Atlas turns your pricing into governed, versioned rules. Agents get bounded quotes that name the rule and catalog version behind every number, and a person approves anything above your limits.

Score your pricing, free Start Sandbox

Approval thresholds

Sample seller

Tallyline Data · data API

  • Enterprise agents

    Verified org, signed contract

    Human approval above $50,000

  • Verified agents

    Known agent identity

    Human approval above $5,000

  • Public agents

    Unverified crawlers and assistants

    Human approval above $500

Below a threshold, the buyer’s own human authorizes payment. Above it, a manager on your team approves, and an executive above the manager cap.

One quote, from publish to approval.

A buyer agent asks over MCP. Atlas prices it from the published catalog and holds it above your limit. Once the buyer submits it, your deal desk approves it with an audit trail.

35 seconds, plays muted. A simplified recreation of the Pro plan with an example seller and buyer agent.

Publish once. Every quote traces back to it.

  1. Import

    Paste a price book, upload a spreadsheet, PDF or screenshot, or pull Stripe or Chargebee products into a draft. Atlas structures plans and meters and flags conflicts. Deep verification checks every price against your source and accounts for every amount it prints: 3 runs a month on Sandbox, 100 on Pro.

  2. Review

    Attach evidence, set who approves what, and try pricing scenarios before anything is live.

  3. Publish

    One publish puts the catalog on every protocol your plan unlocks. Agents only see the version you publish.

  4. Work exceptions

    Approve machine access and work the deal desk.

Pricing accuracy

Agents quote what you actually charge.

A wrong price in front of a buying agent becomes a wrong quote. On Pro, Atlas checks every price against your source before it reaches a draft, and keeps the catalog in step when your pricing changes.

  • Deep verificationEvery price must quote the line it came from, every amount your source prints is accounted for, and anything that cannot be verified is flagged so it cannot be published unchecked.
  • Sync with your pricing pageWhen your page changes, the catalog copilot shows exactly what to update in the catalog, each change quoting the page. You apply it to a draft; nothing publishes on its own.
  • Edit in plain languageAsk for “Raise the Growth platform fee to $550” and see every change before and after, with its risk. When a request could mean more than one offer, the copilot asks.
// Tallyline Data. Source: the seller's pricing page
Requests · per 1K        USD 0.05 → 0.06
  “$0.06 per 1,000 requests”
Growth · Platform        USD 500.00 → 550.00
  “Platform fee: $550 per month”
Add Scale                USD 1,200.00 / month
  “Scale: $1,200 per month”

// 6 of 6 source prices verified · Moderate change risk
// Apply to draft. Nothing publishes until you do.

Quote authority

Agents learn that a quote needs a person. Never where your limit sits.

Atlas enforces your threshold on every protocol your catalog is served on. The agent gets the status, who must approve and what it can do next. Your threshold is never in the response.

  • Per-key limitsEvery agent call is capped by your rules: spend, quote and pricing rates, and what it’s allowed to see. How limits work
  • No order splittingA key’s recent quotes that went through without approval count together toward your cap, so splitting a large order still reaches your deal desk.
  • Retry contractOut-of-policy asks return a stable code that tells the agent to revise, poll for approval or back off.
// Request: 100M requests at $0.06 per 1K
{ "offerId": "api.requests-1k", "units": 100000 }

// Response 201 Created. No threshold amount.
{
  "answerType": "approval-required",
  "binding": false,
  "catalogVersionId": "catv_v7",
  "data": {
    "quoteRequest": {
      "id": "q_4b2d",
      "status": "approval-required",
      "calculation": { "total": "6000.00" },
      "policyDecision": {
        "reasons": [
          "Quote total exceeds autonomous authority."
        ],
        "requiredApprovers": ["deal-desk"],
        "nextAllowedActions": [
          "track-approval",
          "withdraw-request"
        ]
      }
    }
  }
}

Stay in the systems you already run.

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.

  • Restricted keys onlyStripe connections take restricted rk_ keys, encrypted at rest and bound to your organization.
  • Nothing binds earlyQuotes are always non-binding. Your billing system acts only when an agent executes a quote that is in policy or approved by a person. Sandbox rehearses the handoff with Mock mode.

PairRail Atlas

Tallyline Data

catalog v7

  • Lands as a draft invoice or quote by default. See the webhook payload
  • An agent quote opens a deal; an access request or deal-desk item opens a task.
  • Salesforce writeback is coming next. NetSuite already works through the signed webhook.

Using Orb, Metronome or Paddle? The signed webhook works today. Request a native connector.

Go live free in Sandbox. Move to Pro when agents start quoting.

PlanUse it whenWhat buyer agents see
SandboxGetting started: import, verify, publish, and rehearse the billing handoff with Mock mode.Your catalog and indicative prices live on MCP. Quotes are marked as a rehearsal.
ProAgents or procurement tools start asking you for quotes.Live catalogs on MCP, UCP, ACP, A2A and UAP, with your approval rules and retry codes.
EnterpriseYou need contract paper: an MSA, a signed DPA, invoices by wire, or SSO and residency terms in your order form.The same live catalogs as Pro, and each approved buyer's contract price, inside the floors you set.
Score your pricing, free Compare plans and limits