For merchants
Drop the SDK in or work with our team. Either way, your storefront accepts agent payments in days, not quarters.
11
Framework adapters
Node and Python
4
Payment rails
Stripe, Tempo, Solana, Base
Live
In production
Martin Estate, Sayer & Stone
Cross-merchant operator identity
An agent verified at another AgentScore merchant is known the moment it reaches you: less checkout friction, less fraud, and no KYC stack for you to build or maintain. Repeat agents resolve to the same operator on /v1/assess, even from a wallet you have never seen.
Two ways to onboard
Self-serve SDK
Know who's behind every agent. Take the payment. Stay compliant.
npm install @agent-score/commercepip install agentscore-commerceAgentScore Forward-Deployed Engineering
Our engineers embed with your team and ship the integration end-to-end. Martin Estate and Sayer & Stone are the canonical examples.
What's in the SDK
One builder. Every rail you accept. x402 v1/v2 dual-read out of the box.
KYC, age, sanctions, jurisdiction. One middleware call. Auto-mints sessions on missing identity.
Multichain payment intents for Stripe SPT, card, and Link. Wallet capture on settlement.
Skill manifests auto-published at /skill.md, /llms.txt, and OpenAPI.
Framework adapters
Payment rails
Card / Link
Stripe · Shared Payment Token
Tempo
MPP · USDC
Solana
MPP · USDC
Base
x402 · USDC
Live in production today
Martin Estate and Sayer & Stone both ship multi-rail x402/MPP (Stripe SPT, MPP on Tempo and Solana, x402 on Base). Martin layers in AgentScore Gate (KYC, age 21+, sanctions, US-only) because wine is regulated; Sayer & Stone doesn't need to.

When an agent buys a bottle, AgentScore confirms a real, 21+, US, sanctions-clear human is behind it and takes the payment. Real per-state tax at checkout.
Read the case study
Earrings and bracelets, made to order. A modern jewelry brand opens a new customer surface on the same @agent-score/commerce stack.
Pricing