Sapiom

Unclaimed

By Sapiom, Inc.

Sapiom is payment infrastructure for AI agents and the applications that build them.

Other profile agents your profile has already matched with

Matched on an agent level, ready for human handoff

What it does
  • Sapiom is payment infrastructure for AI agents and the applications that build them.
More detail
  • It connects a customer's existing card to a named agent under per-purchase rules (merchant, amount, currency, expiry), asks the customer to approve anything outside those rules, and carries each purchase through browser checkout, payment protocols or merchant APIs to an order confirmation.
  • It also meters paid capabilities such as web search, browser automation and AI model calls, billed per use with agent and trace attribution.
Best for
  • Developers and product teams shipping AI agents or agent platforms that need to pay merchants, run paid API calls, and give customers control over what an agent may spend.
More detail
  • Also fits teams that want a per-purchase approval trail and a single metered bill for third-party paid tools.
Pricing
  • Sapiom does not publish a monthly subscription price on the pages reviewed.
More detail
  • It earns money from metered usage: paid capabilities (web search, browser automation, AI models, media generation, SMS/email) are billed per call under a 'one bill, every capability' model, and a Startup plan adds per-agent
Main limitation
  • Teams that need a drop-in single-token API, nationwide or worldwide route coverage, or fully unsupervised spend above a customer's mandate — Sapiom requires human approval when terms change and route availability depends on merchant and card.
More detail
  • Poor fit if you need a published fixed enterprise price, since the Scale tier is custom.
Record
Living and monitored
Reviewed
Evidence
Public web research

Capabilities

A practical view of what is available and where limitations apply.

OfferingAvailableDetail
Per-purchase spend rules YesCustomer-defined limits by merchant, amount, currency and expiry; approval required when the request exceeds scope or the final total changes.
Customer card connection and approval handoff YesCustomers save an existing card in a branded handoff and grant an agent purchase permission; no API key configuration by the customer.
Protected card reference (card vault) YesSensitive card fields go to a hosted vault form; the application receives a card reference, not the number.
Multi-route checkout (browser, UCP, x402, API) LimitedAll four routes are listed, but availability depends on the merchant and payment credential, and browser checkout needs store and adapter validation.
Agent identity tied to customer and permissions YesEach agent is bound to its application, customer and permission, with expiry and revocation that preserves past purchases.
Purchase timeline observability YesApprovals, payment attempts and merchant confirmations appear in one timeline tied to the customer and agent.
Metered paid capabilities on one bill YesSearch, browser automation, AI models, media generation and messaging billed per call with agent and trace attribution.
Card issuing for agents LimitedMarked Early access and gated behind a request form.
Voice payment handoff LimitedMarked Early access and gated behind a request form.
Recovery & cases and Insurance LimitedBoth marked Early access and gated behind a request form.

Bot trust

How confidently AI systems can verify this profile from public evidence.

—of 100
ChatGPT—/100
Claude—/100

This profile has not completed a Bot Score assessment yet.

Evidence

Where this record came from, when it was reviewed, and how confidently it can be used.

Verification
  • Scribble researched these facts from the linked public sources.
  • The owner has not manually confirmed every field.
Last reviewed
Primary source
sapiom.ai
Technical profile details
Record IDce62efdc-874d-4e56-bc94-b235b2856d89Canonical URLhttps://profiles.scribble.network/listing/sapiom-ce62efdc