Accepting early design partners

The financial firewall
for agentic spend

IntentRails is the runtime policy and tripwire layer for B2B AI agent fleets. PASS, TRIP, or HALT before money moves — composing with Ramp, Stripe Issuing, Lithic, and x402.

Try the Spend Simulator Request API Access

Built for emerging standards

Google AP2 Mastercard Verifiable Intent FIDO Alliance
Spend Simulator

Try an agentic payment before it hits the rail

Pick a task, watch the agent propose a spend, and see whether the FCB returns PASS, TRIP, or HALT before your issuer is involved.

Agent task

Ops lead

Procurement agent

agent.propose() → intentrails.evaluate() → rail.execute()

Runtime evaluation

PASS

Amount
Merchant
Rail 


          

            
            
          

        

      

    

  


  

  
  

    

      

        The Problem
        
Buyer-side agent fleets need more than payment credentials

        

          Scoped cards and tokens are necessary. The missing layer is runtime trust — one policy engine that evaluates intent, fleet velocity, and cumulative drift before any rail moves money.
        

      


      

        
        

          

            
            Issuer-only approach
          

          
Per-card limits

          
Corporate card programs — Ramp Agent Cards, Stripe Issuing, Lithic — enforce amount, merchant, and MCC at authorization, one card at a time.

          

            

              
              
No fleet view — fifty agents can each spend up to the daily cap; cumulative exposure still blows the budget.

            

            

              
              
Authorize-time only — AP2 mandates prove what was signed at setup; they do not ask "should this fire right now?"

            

            

              
              
Single-rail lock-in — finance teams on Ramp cannot reuse the same policy layer for x402 micropayments or a second issuer.

            

          

        


        
        

          

            
            IntentRails approach
          

          
FCB runtime control plane

          
Fiduciary Circuit Breaker sits between your agent and your issuer — deterministic PASS / TRIP / HALT in under 50ms, with an AP2-shaped RiskPayload for audit.

          

            

              
              
Fleet tripwires — velocity, cumulative caps, merchant allowlists, and authority scope across every agent in the fleet.

            

            

              
              
Pre-settlement gate — block rogue spend before your issuer or x402 rail executes the payment.

            

            

              
              
Issuer-agnostic — same policy layer for Ramp, Lithic, Stripe Issuing, and agent micropayments on x402.

            

          

        

      

    

  


  

  
  

    

      

        Market Reads
        
What the ecosystem is already teaching us

        

          Rail builders are making agent payments possible. IntentRails focuses on the buyer-side control layer that decides whether an agent should spend now.
        

      

      

        

          
Prava

          
One-time delegated cards make the agent payment experience legible. IntentRails keeps that clarity but shifts from consumer wallet flow to B2B fleet policy.

        

        

          
Ramp

          
Agent Cards validate corporate agent spend. The open wedge is fleet-level velocity, cumulative exposure, and cross-rail runtime policy.

        

        

          
Nava

          
The propose, verify, execute pattern is the right mental model. IntentRails applies it specifically to buyer mandates before payment execution.

        

        

          
Stripe

          
Agentic commerce protocols are moving quickly. A neutral trust layer helps buyers avoid rebuilding policy every time rails or protocols change.

        

      

    

  


  

  
  

    

      

        Who It's For
        
B2B buyer-side teams making agents safe to transact

        

          Not consumer travel bots or card issuers — platforms where agents buy cloud, SaaS, data, or vendor services on behalf of business customers.
        

      

      

        

          
          
Agent infra & marketplaces

          
Sandbox platforms and agent orchestrators turning copilots into transactors on corporate budgets.

        

        

          
          
Procurement & ops automation

          
Teams whose agents buy cloud, SaaS, or vendor services — need fleet caps beyond per-card limits.

        

        

          
          
Finance + eng leads

          
Already on Ramp, Lithic, or Stripe Issuing — want one runtime trip layer across cards and x402.

        

      

    

  


  

  
  

    

      

        The Protocol
        
One evaluate call. Three outcomes.

        

          IntentRails sits between your agent orchestrator and whatever moves money — card issuer, x402, or AP2 mandate flow.
        

      


      

        

          01
          
          
Agent requests spend + policy context

          
Your B2B agent calls IntentRails with the proposed payment — amount, merchant, rail, and the scoped mandate or corporate policy it claims to satisfy.

          
POST /v1/evaluate
{
  "agent_id": "procurement_bot_7",
  "amount_usd": 500.00,
  "merchant": "aws.amazon.com",
  "rail": "card"
}

        


        

          02
          
          
FCB returns PASS, TRIP, or HALT

          
Deterministic policy checks run in milliseconds — velocity, cumulative spend, merchant allowlists, authority scope. TRIP escalates; HALT blocks before money moves.

          
{
  "verdict": "TRIP",
  "reason": "fleet_velocity_exceeded",
  "risk_payload": { "ap2": "..." }
}

        


        

          03
          
          
Approved spend routes to your issuer

          
On PASS, your platform uses its existing stack — Ramp Agent Card, Lithic virtual card, Stripe Issuing, or x402 — with IntentRails audit trail and AP2 RiskPayload attached.

          
{
  "verdict": "PASS",
  "issuer_handoff": "ramp_agent_card",
  "max_amount": 500.00,
  "merchant_allowlist": ["aws.amazon.com"]
}

        

      

    

  


  

  
  

    

      

        Integrations
        
Composes with your stack — does not replace it

        

          Ramp proves finance teams need agent spend controls. IntentRails standardizes the runtime trip layer across issuers and rails — the AP2 Risk field incumbents will not unify.
        

      

      

        

          
          
Ramp · Lithic · Stripe Issuing

          
Keep your corporate card program. IntentRails evaluates first; your issuer executes on PASS.

        

        

          
          
x402 micropayments

          
Same policy engine for agent API spend — daily caps, velocity trips, merchant allowlists on-chain or off.

        

        

          
          
B2B agent platforms

          
Procurement bots, DevOps agents, and agent marketplaces — turn read-only copilots into safe transactors.

        

      

    

  


  

  
  

    

      

        Standards Compliance
        
Built on 2026 emerging standards

        

          Mandates prove authorization — IntentRails adds runtime risk control and audit on top of each protocol.
        

      

      

        
        

          2026 Standard
          
          
Google AP2

          
Compatible with Google's Agent Payments Protocol — including RiskPayload extensions for runtime tripwires (AP2 #163).

        


        
        

          2026 Standard
          
          
Mastercard Verifiable Intent

          
Composable with Mastercard Verifiable Intent — cryptographic proof of delegated authority; FCB decides whether to fire now.

        


        
        

          2026 Standard
          
          
FIDO / AP2 ecosystem

          
Aligned with FIDO Alliance agentic payment work — audit-friendly RiskPayload records for compliance and dispute evidence.