Your Agent Stack's Shopping List: The Rails Layer of SaaS
Builders talk about agent stacks as models, harnesses, and tools. There is a layer underneath that gets less attention: the things your agent must rent because it cannot generate them. I think of SaaS as three layers, re
Builders talk about agent stacks as models, harnesses, and tools. There is a layer underneath that gets less attention: the things your agent must rent because it cannot generate them. I think of SaaS as three layers, records, workflow, rails, and my prediction is that agents will absorb more of the first two. This post is a practical map of the third.
The two layers your agent absorbs
Records. A simple CRM can be built over a database. If an agent reads and writes the record, a custom Postgres-backed application may replace some record-entry software. That is not the same as replacing enterprise permissions, business semantics, audit, migration and support. This is mainstream enough that Supabase has a "for agents" solution page and people publish build-your-own-CRM tutorials with an agent plus Supabase. Caveat: compliance-heavy records keep their wraparound value.
Workflow. Boards and pipelines told humans what to do next. The harness now holds the plan; the human sees a task list only when a decision is needed. Notice the direction of connectors: Apollo's official MCP server puts prospecting inside Claude/ChatGPT with OAuth, rather than pulling you into Apollo's UI.
What remains is what this post is about.
Rail 1: Payments (the most built-out)
Four concrete systems you can integrate or study today:
- ACP (Agentic Commerce Protocol, Stripe + OpenAI). Powers Instant Checkout in ChatGPT. Open standard, merchant keeps fulfillment control, works across processors.
- AP2 (Agent Payments Protocol, Google). Signed Intent and Cart Mandates via verifiable credentials: a non-repudiable audit trail from instruction to payment, including delegated purchases with price limits. 60+ backers: Adyen, Amex, Coinbase, Mastercard, PayPal, Salesforce, ServiceNow.
- x402 (Coinbase). The HTTP 402 status code, revived: stablecoin micropayments per API call over plain HTTP. The cleanest fit for agent-pays-for-API flows.
- ChatGPT Wallet (OpenAI, Nov 2026). User approves each purchase with biometrics; the network issues a tokenized card number; the agent never sees card details.
Design note: these systems have different payment and authorization models. AP2 describes mandates, while Wallet describes per-purchase approval and tokenized card details. Do not assume one protocol supplies the controls of another.
Rail 2: Voice and telephony
Voice agents rent the dial tone. Retell publishes headline voice-agent pricing at $0.07-$0.31/min, decomposed into infra ($0.055/min), voices ($0.015-$0.10/min depending on provider), and per-minute LLM rates. Check telephony, model, voice and optional add-on charges separately before estimating a deployment. Numbers, caller ID reputation, and telephony compliance are regulated and scarce; treat them as dependencies, not features.
Rail 3: Contact and company data
Your agent cannot invent a prospect's real email. Apollo and Hunter both now sell to the agent directly (MCP servers, OAuth, "Hunter for AI & Agents"). These interfaces are evidence of vendors supporting agent access alongside dashboards, not proof that human buyers or dashboards are disappearing.
Rail 4: Identity and authorization
"Who is this agent and what may it do" is unresolved and actively standardized: IETF drafts for agent identity (WIMSE), OIDC agent identity claims, and OAuth profiles for agents. Vendors (WorkOS and friends) already sell agent auth guidance and plumbing. SSO-for-agents will be bought, not built.
Rail 5: Inboxes, browsers, calendars, audit
- Inboxes/messaging: deliverable email/SMS with reputation (Bird's Mailbox API "for AI agents" is one example).
- Browsers: where no API exists, rent cloud browser sessions (Browserbase/Stagehand). Rail of last resort, shrinking as MCP spreads.
- Calendars: availability is state; book through calendar APIs.
- Audit: when agents spend or sign, someone stores proof of authority. AP2 mandates are the early shape.
The test
A rail is anything scarce, regulated, or stateful that your agent needs. Money movement, reachability, identity, verified data, proof. Decide which records and workflows can move into your harness, preserve human approval where needed, and budget for external services. Being a rail does not guarantee pricing power or protection from competitors.
Originally researched for the Predicting Future newsletter. Sources and dates: openai.com (ChatGPT Wallet, Nov 13 2026), stripe.com (ACP, Sep 29 2025), cloud.google.com (AP2, Sep 16 2025), coinbase.com (x402, May 6 2025), retellai.com/pricing, apollo.io/product/mcp, hunter.io/agents, supabase.com/solutions/agents, datatracker.ietf.org. All checked Nov 22, 2026.
Evidence limit: vendor pages establish that tools exist, not that enterprise SaaS has been displaced. A system of record still needs an accountable owner and consistent rules. Relevant sources: Supabase, Apollo, Wallet, AP2, Retell pricing.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.