# AsterPay β€” Full documentation (machine-readable concatenation) > Generated 2026-07-18 from 70 pages on https://asterpay.io. > Site index: > One-shot ingest: read this file end-to-end for full AsterPay context. --- # AsterPay Data API - x402 Payment API Source: Markdown mirror: [πŸ“¦ AsterPay Data API](/) [Endpoints](#endpoints) [Documentation](/docs) [AsterPay](https://asterpay.io) # The First x402 Payment API Pay per request with USDC. No subscriptions, no credit cards. Just instant micropayments for AI agents and developers. [View Documentation](/docs/) [Explore Endpoints](#endpoints) ## Why x402? ### ⚑ Instant Payments Pay per request, no subscriptions. Perfect for AI agents making autonomous payments. ### πŸ’° Micropayments Pay from $0.001 per request (typical $0.01, range $0.001–$0.10 by endpoint). QR code endpoint free. No minimums, no commitments. ### πŸ€– AI Agent Ready Native x402 support means AI agents can pay automatically without human intervention. ### 🌐 No Account Required Just pay and use. No registration, no credit cards, no KYC. ## API Endpoints ## Market Data GET /v1/market/price/:symbol FREE GET /v1/market/ohlcv/:symbol FREE GET /v1/market/trending FREE ## AI Tools POST /v1/ai/summarize FREE POST /v1/ai/sentiment FREE POST /v1/ai/translate FREE POST /v1/ai/code-review $0.05 ## Crypto Analytics GET /v1/crypto/wallet-score/:address $0.05 GET /v1/crypto/token-analysis/:address $0.10 GET /v1/crypto/whale-alerts FREE ## Utilities POST /v1/util/qr-code FREE POST /v1/util/screenshot FREE POST /v1/util/pdf-generate FREE ## Authentication AsterPay uses one rule per surface. You almost never need an API key. | | Surface | Auth | How | Free read endpoints trust score, settlement estimate, discovery, market rates | None | Plain HTTP GET. No key, no account. | Paid endpoints deep analysis, offramp, AI tools, crypto analytics | Pay-per-call (keyless) | x402 `PAYMENT-SIGNATURE` header, or MPP `Authorization: Payment`. No account. | Dashboard & merchant features usage analytics, settlement payouts (app.asterpay.io) | API key | `Authorization: Bearer sk_...`. Only for dashboard-bound calls β€” never required for the public API above. Live payout requires KYB (handled at settlement, not at the API). Reads and per-call payments stay keyless and accountless. ## Example Usage ``` // FREE read endpoint β€” no key, no payment const est = await fetch( 'https://x402.asterpay.io/v1/settlement/estimate?amount=100' ).then(r => r.json()); console.log(est.data.netEurAmount, est.data.estimatedSepaTime); // PAID endpoint β€” easiest path is the x402 fetch wrapper, which // auto-handles the 402 -> pay -> retry loop for you. // npm install x402-fetch (USDC on Base, EIP-3009, mainnet) import { wrapFetchWithPayment } from 'x402-fetch'; import { account } from './wallet.js'; // your funded signer const pay = wrapFetchWithPayment(fetch, account); const data = await pay( 'https://x402.asterpay.io/v1/agent/deep-analysis/0xYourAgentAddress' ).then(r => r.json()); // The wrapper reads the 402 challenge (x402Version 2, network eip155:8453, // USDC asset), signs an EIP-3009 transferWithAuthorization, base64-encodes it, // and retries with the PAYMENT-SIGNATURE header. You just get the result. ``` Prefer raw HTTP or another language? The full request/response shapes are in the [OpenAPI 3.1 spec](https://asterpay.io/openapi.json), the [Postman collection](https://asterpay.io/postman/asterpay.postman_collection.json), and the [interactive docs](/docs/). Every paid call also accepts MPP (`Authorization: Payment`) on the same URL. Β© 2026 AELIRA LTD (HE 490977) | [asterpay.io](https://asterpay.io) | [@Asterpayment](https://twitter.com/Asterpayment) --- # Coinbase Bazaar β€” AsterPay live discovery check Source: Markdown mirror: > Search the public Coinbase CDP x402 Bazaar discovery feed live and confirm AsterPay [AsterPay](/) [Docs](/docs) [Trust Center](/trust) [API](/api) [Raw feed β†—](https://x402.asterpay.io/bazaar) Verified on Coinbase Bazaar # AsterPay is discoverable by AI agents. Search the public Coinbase CDP x402 discovery feed live, right here. This is the same feed AWS Bedrock AgentCore reads β€” type anything and see AsterPay's indexed endpoints. Search AsterPay KYA agent trust score agent wallet sanctions USDC to EUR settlement crypto prices Source: `api.cdp.coinbase.com/platform/v2/x402/discovery/search` β€” the public Coinbase CDP discovery feed (no API key). Results are live. Coinbase recomputes search ranking on a periodic quality cycle, so brand-new endpoints can take a cycle to rank for generic terms. Β© 2026 AELIRA LTD Β· AsterPay Β· Cyprus HE 490977 [Trust Center](/trust) Β· [Docs](/docs) Β· [Home](/) --- # /blog/agent-constitution/_build/banner.html Source: Markdown mirror: { } AsterPay KNOW YOUR AGENT VERIFIABLE ON-CHAIN COMMITMENT # Agent Constitutions Proving what an AI agent promised β€” before a cent moves. hash = sha256(canonicalize(policy)) β†’ ERC-8004 Identity Β· Reputation Β· Commitment --- # /blog/agent-constitution/_build/code.html Source: Markdown mirror: constitution.json ``` { "version": 1, "agent": { "wallet": "0x...", "agentId": "16850" }, "spending": { "perTxMaxUsd": 1000, "dailyMaxUsd": 5000 }, "rails": { "allowed": ["x402", "mpp"], "chains": ["base"], "tokens": ["USDC", "EURC"] }, "counterparties": { "mode": "open" }, "risk": { "killSwitchOnSanction": true }, "issuedAt": "2026-06-27T00:00:00.000Z" } ``` --- # Agent Constitutions: Proving What an AI Agent Promised | AsterPay Blog Source: Markdown mirror: > Identity tells you who an agent is. Reputation tells you what others think. Neither tells you what it committed to. A small, verifiable mechanism: canonical-hash an agent [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / Agent Constitutions # Agent Constitutions: Proving What an AI Agent Promised Know Your Agent has two solved axes and one missing one. Identity tells you who an agent is. Reputation tells you what others think of it. Neither tells you what it has committed to do, or lets you prove it later. Here is the small, verifiable mechanism that closes the gap. June 27, 2026 4 min read By Petteri Leinonen, Founder, AsterPay When an autonomous agent shows up to move money, a counterparty asks three different questions. Who is this? is identity: an on-chain registry like ERC-8004, operator KYB, sanctions screening. What does the network think of it? is reputation: history, endpoint quality, third-party signals. Both are well covered. The third question is the one nobody answers: what has this agent actually committed to do, and can I verify it? Identity is who. Reputation is what others think. A constitution is what the agent promised, in a form anyone can check. ## A constitution is a hashed, committed policy An agent constitution is a machine-readable declaration of the rules an agent operates within: spend caps, allowed payment rails, chains and tokens, counterparty mode, and a kill-switch on sanctions. It is plain data. ``` { "version": 1, "agent": { "wallet": "0x...", "agentId": "16850" }, "spending": { "perTxMaxUsd": 1000, "dailyMaxUsd": 5000 }, "rails": { "allowed": ["x402", "mpp"], "chains": ["base"], "tokens": ["USDC", "EURC"] }, "counterparties": { "mode": "open" }, "risk": { "killSwitchOnSanction": true }, "issuedAt": "2026-06-27T00:00:00.000Z" } ``` The agent computes a canonical SHA-256 hash of that policy and commits the hash to its own ERC-8004 identity metadata under the key `constitution`. The hash is the commitment. The policy stays readable; the chain holds the fingerprint. ## Canonicalization is the part that matters A hash is only useful if two parties computing it independently get the same value. JSON does not guarantee that, because key order and whitespace vary. So before hashing we canonicalize: sort object keys, drop insignificant whitespace, keep array order. `{a,b}` and `{b,a}` must produce an identical byte string and therefore an identical hash. ``` canonicalize(policy) // JCS-style: keys sorted, no whitespace, arrays in order hash = "0x" + sha256(utf8(canonical)) ``` Now verification is a pure function. Re-canonicalize the stored policy, re-hash it, and compare to the value committed on-chain. No service trust required, no internal state: any third party with the policy and the chain can reproduce the result. ``` local = sha256(canonicalize(policy)) onChain = readErc8004Metadata(agentId, "constitution") match = normalize(local) === normalize(onChain) ``` Tamper-evident by construction. If the agent quietly edits its policy, the recomputed hash no longer matches the on-chain commitment, and the mismatch is visible to anyone. A promise you can change without anyone noticing is not a promise. ## We never hold the agent's key The on-chain commit is signed by the agent with its own key. AsterPay computes the canonical hash, stores the policy so it can be served and re-hashed, and verifies the match. We are the verifier, not the signer. This is deliberate: the party that declares the policy is the party that signs the commitment, and a verification service that cannot move your funds is a smaller thing to trust. ## What this does, and what it does not Be precise about the boundary. A constitution proves an agent published and committed to a policy. Enforcement still happens at the application layer, where each payment is checked against the committed rules before it is allowed. The hash does not make an out-of-policy transaction physically impossible to sign. Making it impossible is the next layer: move policy enforcement to the signing key itself, inside a trusted execution environment, so a transaction that violates the constitution cannot be produced at all. The constitution is the public, verifiable contract; key-level policy is what turns "committed to" into "cannot exceed." The first is shippable today and stands on its own; the second builds on it. ## One more input to Know Your Agent A committed, verified constitution is a real risk signal. An agent that has publicly bound itself to a 1,000 USD per-transaction cap is in a different class from one with no declared limits. It joins identity and reputation as a third axis of the KYA trust score, and like the rest of the score it is deterministic and reproducible, not a black box. ### Know Your Agent, before money moves Verify identity, screen for sanctions, score any agent wallet 0-100, then settle to EUR. Free to query, no signup. [How KYA works](/learn/know-your-agent-compliance-eu/) [Read the docs](/docs/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # The Agentic Discovery Layer Has Two Floors | AsterPay Blog Source: Markdown mirror: > Winning AI visibility gets an agent to your door. The floor below decides whether it can actually pay you, and whether you should let it. Why payment discovery, trust, and settlement are the other half of the discovery layer. [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / The Agentic Discovery Layer Has Two Floors # The Agentic Discovery Layer Has Two Floors There is a good conversation happening right now about winning the discovery layer: showing up in AI answers, optimizing for multi-step conversations instead of single prompts, building visibility before the ads arrive. It is all correct. It is also only the top floor. June 23, 2026 5 min read By Petteri Leinonen, Founder, AsterPay The marketing world has woken up to a real shift. Discovery is moving from search results to AI answers, and the people who understand how an assistant forms a recommendation across a multi-turn conversation will have an edge over the people still chasing single keywords. I agree with all of it. But the same articles point to the thing that makes this urgent, and then walk right past it. They note that OpenAI and Stripe have shipped in-chat checkout, that Walmart is letting people buy inside ChatGPT, that recommendation and transaction are converging. That convergence is exactly the point. When the line between "the agent recommends you" and "the agent pays you" disappears, visibility stops being the finish line. It becomes the entrance. Getting recommended is the top floor. Getting paid, safely, is the floor below, and that is where the money actually changes hands. ## Floor one: be findable. Floor two: be payable Floor one is the discovery everyone is writing about. Does your brand show up when an agent researches the category? Do the right signals, citations, and structured data push you into the recommended set? Lose here and you are invisible. Fair enough. Floor two is what happens the instant the agent decides to act. It is a different stack of problems, and almost nobody in the marketing conversation is naming it: - Payment discovery. The agent has chosen you. Now where does it send the money? It needs a machine-readable, verified payment endpoint: which account, on which rail, confirmed to actually belong to you. - Trust, in the other direction. An agent showing up to pay is not automatically a good thing. Is it who it claims to be? Is it acting for a real principal? Is the wallet clean? You are now the one accepting a stranger's money, autonomously, at machine speed. - Settlement. A stablecoin landing on a wallet is not euros in your bank. The transaction is only finished when value arrives as real money you can spend. Floor one decides whether the agent finds you. Floor two decides whether you get paid and whether you should have accepted the payment at all. You can be perfectly optimized for AI visibility and still have no answer to either question. ## Discovery without trust is just a wider door for fraud Here is the uncomfortable version. The better you get at floor one, the more agents arrive at floor two. Some of them you do not want. The same week I write this, a wallet listed directly on the OFAC sanctions list knocked on one of our endpoints and tried to pay. It was screened and blocked before a single cent moved. That is not a hypothetical. When buyers are autonomous software arriving by the thousand, "who is paying me" becomes a question you cannot answer by looking at a face. This is what Know Your Agent is for. KYC and KYB ask whether a person or a business is legitimate. KYA asks the same of autonomous software, before money moves: verify identity through an on-chain registry like ERC-8004, screen the wallet against sanctions lists in real time, and compress behavior into a single trust score a counterparty can act on. Visibility brings agents to your door. Trust decides which ones you let through it. Floor two has its own optimization problem. Just as floor one rewards structured data and clear signals, floor two rewards a verified payment endpoint and a readable trust posture. An agent that cannot resolve how to pay you, or cannot trust that it is really you, moves on to the brand it can. ## How to prepare for the floor nobody is talking about The GEO playbook says: treat AI as its own channel, move beyond single prompts, analyze the signals, build discovery intelligence before the ads arrive. Good advice. Here is the parallel checklist for floor two. - Be discoverable as a payable endpoint, not just as a brand. Publish a machine-readable way for an agent to find how to pay you, the same way you publish content for it to read. A name an agent can resolve to a verified account beats a contact form it cannot use. - Make yourself verifiable. An agent about to send money wants proof the destination is really you. Verified payment details and a disclosed verification method are the floor-two equivalent of authoritative citations. - Screen the agents you accept. Do not wait for a chargeback that does not exist in crypto. Screen inbound agents for sanctions, identity, and behavior before you accept, not after. The cost of getting this wrong is regulatory, not just financial. - Settle in real money. Decide now how a stablecoin payment becomes euros in your account, with finality, in seconds. If your answer is "we will figure out the off-ramp later," you do not have a payment system. You have an IOU on a wallet. ## The brands that win are visible, payable, and trusted The biggest mistake in this moment is to treat agentic commerce as an SEO problem with a new vocabulary. Visibility is necessary and it is not sufficient. The brands that win the agent economy will be the ones an agent can find, can pay, and can trust, and the ones who can trust the agent back. That is a two-floor building. Most people are only furnishing the top. AsterPay builds the second floor. A Merchant Payment Endpoint so agents can discover a verified way to pay you, a Know Your Agent trust layer (ERC-8004 identity, real-time sanctions screening, a 0-100 trust score) so you know who is paying, and non-custodial EUR settlement via SEPA Instant so the money lands as real euros. We never hold the funds. ### See floor two in action Score any agent wallet before you accept its payment. Free, no signup. [How KYA works](/learn/know-your-agent-compliance-eu/) [How agents find your account](/blog/how-agents-find-merchant-iban/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # AI Agent Payments in Europe: MiCA, SEPA Instant, and the Agentic Commerce Stack | AsterPay Source: Markdown mirror: > How AI agents transact in Europe under MiCA regulation. Guide to compliant AI agent payments, SEPA Instant settlement, and the emerging agentic commerce infrastructure in the EU. [AsterPay](/) [All Articles](/blog/) [Home](/) / [Blog](/blog/) / AI Agent Payments in Europe # AI Agent Payments in Europe: MiCA, SEPA Instant, and Agentic Commerce Autonomous AI agents are starting to transact billions. In Europe, they need MiCA-aligned partner routing, SEPA Instant settlement, and proper identity. Here's the infrastructure stack making it happen. Published March 15, 2026 9 min read By AsterPay $1-5T Agentic Commerce by 2030 450M+ EU Population (Single Market) <10s SEPA Instant Settlement ## The Agentic Commerce Revolution McKinsey estimates AI agents will drive $1-5 trillion in commerce by 2030. These autonomous software agents book flights, purchase API services, compare prices, and execute transactions β€” without human intervention. But agents can't use credit cards. They don't have names. They can't fill out checkout forms. The existing payment infrastructure was built for humans, not machines. This is where agentic commerce infrastructure comes in β€” a new category of payment rails purpose-built for autonomous AI agents. ## Europe's Unique Position Europe is the most attractive market for compliant agentic commerce because of three regulatory advantages: ### 1. MiCA (Markets in Crypto-Assets Regulation) MiCA took full effect in 2025, creating the world's first comprehensive regulatory framework for stablecoins and crypto-assets. This means: - USDC and EURC are legally regulated in the EU - Businesses can accept stablecoin payments with legal certainty - Off-ramp providers operate under clear compliance rules ### 2. SEPA Instant (Mandatory) All EU banks must now support SEPA Instant, enabling real-time EUR transfers 24/7/365. This means stablecoin-to-EUR settlement can happen in seconds, not days. ### 3. Digital Markets Act + AI Act The EU's regulatory framework creates trust β€” essential for enterprise adoption of AI agent payments. Companies know that AI transactions in Europe operate under clear rules. ## The AI Agent Payment Stack for Europe For AI agents to transact in Europe, five layers must work together: - Agent Identity β€” who is this agent? Who operates it? (ERC-8004, Know Your Agent) - Payment Protocol β€” how does the agent pay? (x402 by Coinbase, AP2 by Google) - Compliance β€” is this transaction legal? (sanctions screening, Travel Rule, MiCA) - Settlement β€” how does the merchant receive EUR? (SEPA Instant off-ramp) - Trust Scoring β€” how much can this agent transact? (progressive limits based on history) AsterPay provides all five layers in one API. We call it the "Agent Trust Framework" β€” the only payment stack built specifically for AI agents transacting in Europe. [Learn more](/) ## Know Your Agent (KYA): The Missing Piece Traditional KYC (Know Your Customer) doesn't work for AI agents. You can't ask an AI bot for a passport scan. Instead, we need KYA β€” Know Your Agent : - On-chain identity : ERC-8004 registration (like AsterPay's Agent #16850 on Base) - Operator verification : Who deployed this agent? Are they a legitimate entity? - Trust Score : A 0-100 rating based on transaction history, attestations, and behavior - Progressive limits : New agents start with $1 limits; established agents get $10,000+ This is analogous to a credit score for machines. The more an agent proves itself trustworthy, the more it can transact. ## How It Works in Practice Consider a European SaaS company that offers an API for real-time financial data. They want AI agents to pay per call: ``` // 1. Add x402 middleware to your API app.use('/v1/*', x402Middleware({ facilitator: 'https://x402.asterpay.io', price: '0.01', currency: 'USDC' })); // 2. An AI agent hits your endpoint // β†’ Agent pays 0.01 USDC via x402 // β†’ AsterPay verifies payment + screens for sanctions // β†’ API returns data to the agent // 3. You receive EUR // β†’ AsterPay settles USDC to EUR via SEPA Instant // β†’ EUR arrives in your IBAN in The merchant never touches crypto. They just get euros. The agent never fills out a form. It just pays per call. ## The Market Opportunity Several converging trends make now the right time: - OpenAI, Anthropic, Google are all building agent frameworks (Agents SDK, MCP, Gemini) - Coinbase launched x402 and AgentKit for on-chain agent payments - Circle's USDC hit $81B market cap, with EURC growing fast in the EU - SEPA Instant became mandatory, enabling real-time EUR settlement - MiCA provided regulatory clarity for stablecoin transactions The infrastructure is ready. The question is: who will be the Stripe for AI agents in Europe? ## Getting Started Whether you're building AI agents or accepting payments from them: - For AI agent developers : `npx @asterpay/mcp-server` or `pip install asterpay` - For API monetization : Add x402 middleware β€” [documentation](/docs/) - For EUR settlement : [Apply at asterpay.io/partners](/partners/) ### Build the Agentic Commerce Stack Europe's AI agent payment infrastructure starts here. MiCA-aligned via licensed partners. SEPA Instant. Agent-native. [Create Free Account](https://app.asterpay.io/signup) [Apply for Settlement](/partners/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # AWS Just Added x402 Monetization. What EU Publishers Do With the USDC | AsterPay Blog Source: Markdown mirror: > AWS WAF now lets publishers charge AI bots via x402 and get paid in stablecoins. The payout lands as USDC on a wallet, not EUR in a bank. Here is how EU publishers close that last mile. [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / AWS x402 Monetization # AWS Just Added x402 Monetization. What EU Publishers Do With the USDC AWS WAF can now charge AI bots for access and pay you in stablecoins. That is a huge validation for x402. But the payout lands as USDC on a wallet, not EUR in a bank account. For European publishers, that last mile is the whole problem. June 16, 2026 4 min read By Petteri, AsterPay On 15 June 2026, AWS announced AI traffic monetization in AWS WAF. When an AI bot or agent requests a protected article, data feed, or API, AWS WAF returns an HTTP 402 Payment Required using the x402 open protocol, verifies the payment at the edge, issues a scoped access token, and serves the response in a single request cycle. Settlement and verification run through Coinbase's x402 Facilitator, with Stripe and MPP support announced as coming soon. This is a big deal. When a hyperscaler ships x402 at the edge of its CDN, machine-to-machine payments stop being a crypto experiment and become infrastructure. The entire category just got more credible overnight. ## The detail that matters for Europe Read the payout mechanics carefully: AWS pays publishers in stablecoins to a preferred wallet . That is great if you want to hold USDC on Base. It is not great if you are a European business that needs euros in a bank account to pay salaries, suppliers, and taxes. The gap: AWS handles pricing, verification, and the stablecoin payout. It does not convert that stablecoin to fiat. For an EU publisher, the money arrives one step short of usable. Someone still has to turn USDC into EUR, compliantly. ## Closing the last mile This is exactly the layer AsterPay was built for. You keep AWS WAF doing what it does best, charging agents and collecting USDC, and add a settlement step on top: - AWS WAF collects USDC from agents into your wallet, as designed. - On a schedule or threshold, you send that USDC to AsterPay's settlement API with your IBAN. - We convert USDC or EURC to EUR and pay it out via SEPA Instant in under 10 seconds . It is non-custodial : we never hold your funds, and the conversion and EUR payout are performed by a licensed European partner, so the regulated activity sits with an authorized entity. MiCA-aligned by design, with the Travel Rule automated. How they fit together: AWS monetizes the traffic and collects the stablecoin. AsterPay turns those proceeds into euros in your account. If you already accept agent payments through x402 or MPP, the EUR off-ramp is one API call away. ## What this means if you build in Europe The takeaway for European publishers and builders is simple. The machine-payment rails are now being standardized by the biggest names in tech, which takes the integration risk out of accepting agent payments. The open question is no longer whether to support x402, it is how to turn the stablecoin proceeds into euros, compliantly. AsterPay accepts both x402 and MPP on every paid endpoint today, so agents pay with whichever SDK they already have, and settlement to EUR happens on top. The rails are becoming infrastructure. The euro settlement layer on top of them is where European builders have home advantage. ### Turn agent payments into euros Non-custodial USDC and EURC to EUR via SEPA Instant. x402 and MPP supported today. [Create a free account](https://app.asterpay.io/signup) [How EUR settlement works](/learn/what-is-x402-eur-settlement/) Source: [AWS WAF announces AI traffic monetization](https://aws.amazon.com/about-aws/whats-new/2026/06/aws-waf-ai-traffic-monetization/) (15 June 2026). [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # Coinbase Commerce Is Shutting Down β€” What European Merchants Should Do Next | AsterPay Blog Source: Markdown mirror: > Coinbase Commerce shuts down March 31, 2026 for non-US merchants. Here [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / Coinbase Commerce Shutdown # Coinbase Commerce Is Shutting Down. What Now? On March 31, Coinbase Commerce stops serving merchants outside the US and Singapore. If you're a European business accepting crypto payments, here are your options. March 26, 2026 5 min read By AsterPay Deadline: March 31, 2026. After this date, Coinbase Commerce becomes inaccessible for non-US/Singapore merchants. Funds must be withdrawn before the shutdown. ## What's happening Coinbase is [shutting down Coinbase Commerce](https://www.ainvest.com/news/coinbase-commerce-shutdown-migration-flows-capital-flight-risk-2603/) for all merchants outside the United States and Singapore. The March 31, 2026 deadline is final. This affects thousands of European businesses that use Coinbase Commerce to accept crypto payments β€” SaaS companies, API providers, marketplaces, and e-commerce shops. Coinbase is consolidating its business platform and focusing on its [x402 protocol](https://docs.cdp.coinbase.com/x402/welcome) and CDP infrastructure. Commerce merchants need to migrate before the deadline. ## What European merchants need If you're an EU/EEA business that was using Coinbase Commerce, you need a replacement that does three things: - Accept stablecoin payments β€” USDC, EURC, or other stablecoins from customers or AI agents - Settle to EUR β€” convert those stablecoins to euros in your bank account - Stay compliant β€” MiCA comes into full effect July 1, 2026. Your payment infrastructure needs to be ready. ## Your options The market has several EUR off-ramp providers β€” from institutional-grade stablecoin issuers to retail on-ramps. The right choice depends on your use case, volume, and whether you need to support autonomous AI agents. For AI agents, APIs, and SaaS: You need a solution that works without human checkout flows, supports machine payment protocols (x402, MPP), and settles to EUR automatically. That's what AsterPay is built for β€” SEPA Instant in under 10 seconds, 0.5% + €0.10 per settlement, MiCA-aligned via licensed partners. ## If you're building for AI agents This is where the landscape has shifted most since Coinbase Commerce launched. AI agents now transact autonomously using protocols like x402 (Coinbase's own standard) and MPP (Stripe/Tempo). These agents need payment infrastructure that works without human intervention. Coinbase Commerce was never designed for this. It was built for checkout flows with human buyers. The new generation of payment infrastructure is built for machines. Context: Coinbase Commerce was built for human checkout flows. Coinbase's focus has shifted to x402 β€” a protocol purpose-built for machine-to-machine payments. The x402 ecosystem continues to grow through independent facilitators. ## What AsterPay offers AsterPay is a settlement API built specifically for AI agent commerce in Europe. Three layers: - Trust (KYA) β€” Know Your Agent scoring. Before any money moves, verify the agent's identity, check sanctions, and assess trust (0-100 score). Free API, no signup. - Discovery (MPE) β€” Your agent knows the company name but not where to pay. AsterPay resolves the IBAN only from provable sources (verified registry, the merchant's signed manifest, or a structured e-invoice) with logged provenance and discloses the Verification of Payee method, with bank-side PSD2 VoP performed by the licensed settlement PSP. - Settlement β€” USDC/EURC to EUR via SEPA Instant. Under 10 seconds. 0.5% + €0.10 per settlement. Both x402 and MPP protocols are accepted on every paid endpoint. Your agents use whichever SDK they already have. ### Try it now (no signup) ``` # Check an agent's trust score (free) curl https://x402.asterpay.io/v1/agent/trust-score/0x1234... # Get a settlement estimate (free) curl https://x402.asterpay.io/v1/settlement/estimate?amount=100 # Full API docs # https://x402.asterpay.io/docs ``` Non-custodial architecture. AsterPay never holds your funds. Payments are verified on-chain and settled to your bank account via SEPA Instant. ## The bigger picture The Coinbase Commerce shutdown isn't just a migration event β€” it's a signal. The era of human-centric crypto checkout pages is giving way to machine-native payment protocols. In the same month: - Stripe and Tempo launched MPP (Machine Payments Protocol) with Visa, Mastercard, Anthropic, and OpenAI - Mastercard acquired BVNK for $1.8B β€” validating stablecoin settlement infrastructure - ERC-8004 (AI Agent Identity) passed 24,000 registered agents - MiCA full enforcement is 3 months away European merchants who need to accept payments β€” from humans or machines β€” need infrastructure that's built for what comes next, not what came before. ### Ready to move? No signup required. Start with the free API endpoints. [API Docs](https://x402.asterpay.io/docs) [USDC β†’ EUR Guide](/blog/usdc-to-eur-settlement) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # First Call Free: What Weeks of 402 Telemetry Taught Us About Agent Conversion | AsterPay Blog Source: Markdown mirror: > Agents were discovering our x402 API around the clock and paying almost never. We audited the telemetry and shipped four fixes: free EUR estimates, first call free per wallet, example responses inside every 402, and a paid agent-readiness endpoint. [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / First Call Free # First Call Free: What Weeks of 402 Telemetry Taught Us About Agent Conversion Agents were discovering our API around the clock β€” monitors, directory indexers, real frameworks probing the 402 flow β€” and paying almost never. We audited every notification and concluded the problem wasn't technical. It was the funnel. Here are the four fixes we shipped today. July 4, 2026 5 min read By Petteri Leinonen, Founder, AsterPay If you run an x402 or MPP API, you get a very particular kind of traffic. Uptime monitors probing your 402 envelope every fifteen minutes. Directory crawlers keeping their catalogues fresh. Agent frameworks doing capability discovery. It all looks like interest, and none of it is a purchase decision. When we separated that infrastructure traffic from genuinely new callers, the picture was uncomfortable but clear: real agents were reaching our paywall, reading a spec-correct 402 challenge with everything they needed to pay β€” and leaving. The payment rail worked. The offer didn't. A 402 challenge is a sales page rendered as JSON. We had been treating it as an error message. ## Fix 1: The shop window is now free Our most-probed endpoint was `GET /v2/x402/offramp/estimate` β€” the USDC-to-EUR settlement estimate. It cost $0.005. That was exactly backwards: the estimate is the shop window, and the 0.5% + €0.10 fee on the settlement itself is the product. Nobody charges you to look at the menu. ``` curl "https://x402.asterpay.io/v2/x402/offramp/estimate?amount=100" # β†’ 200, free # { "outputAmount": 91.83, "outputCurrency": "EUR", # "estimatedDelivery": "10 seconds (SEPA Instant)" } ``` Locking a rate (`POST /v2/x402/offramp/quote`) stays paid β€” that is where a caller signals real intent. ## Fix 2: First call free, per wallet The deepest friction in machine payments isn't price, it's the first commitment. An agent (or its developer) has to wire up a wallet, sign an EIP-3009 authorization, and spend real money on an API it has never seen return a byte. So we removed the spend from the first step. If a payer wallet has never paid AsterPay before, its first call to any endpoint priced at $0.02 or less works like this: - The agent sends a normally signed `PAYMENT-SIGNATURE` β€” zero integration changes. - We verify the EIP-712 signature locally, then check funding, nonce and expiry through the verify path. - We serve the response and never broadcast the authorization . Nothing settles. The first call costs $0. Why this doesn't get farmed: verification requires the wallet to actually hold the USDC it signed for. Spinning up throwaway wallets means funding every one of them β€” at which point you may as well pay the two cents. One free call per wallet, persisted server-side. For us, a first-call-free grant is also the highest-intent signal our telemetry can produce: a funded wallet that took the trouble to sign a valid authorization is not a crawler. ## Fix 3: Show the goods inside the 402 Before today, our 402 told an agent everything about how to pay and nothing about what it would get . Now every challenge on our main endpoints embeds an `example_response` β€” a short, truthful sample of the 200 body: ``` HTTP/1.1 402 Payment Required { "accepts": [ ... ], "example_response": { "prices": { "BTC": 109432.5, "ETH": 3921.14, "SOL": 212.87 }, "sources": 3 }, "first_call_free": { "eligible_endpoint": true, "how": "Retry with a normally signed PAYMENT-SIGNATURE...", "one_per_wallet": true } } ``` An agent evaluating ten APIs for a task can now rank ours on actual output structure instead of a one-line description. That is the difference between being indexed and being chosen. ## Fix 4: Sell what only we have Commodity data doesn't convert β€” an agent can get crypto prices in fifty places. What converts is data with no substitute. So the scan that powers the agent-readiness checker on our homepage is now a machine-callable paid endpoint: ``` GET /v2/x402/agent-readiness?url=example.com # $0.02 via x402/MPP # β†’ { "score": 60, "bucket": "partial", # "signals": { "discoverable": ..., "payable": ... }, # "top_gaps": [{ "label": "Agents can't pay you yet" }] } ``` It scores any public site 0–100 on MCP transport, `agent.json`, `llms.txt`, OpenAPI validity and x402 payability β€” the same published methodology, SSRF-guarded, priced inside the first-call-free window so trying it is free. ## The meta-lesson Machine customers read everything and forgive nothing. A human developer might tolerate a paywalled estimate, an opaque 402, and a "trust us" value proposition, because a landing page talked them into it. An agent just moves to the next entry in the directory. In agent commerce, your protocol surface is your marketing. ### Try it β€” the first call is on us No sign-up, no API key. Hit a paid endpoint, read the 402, retry with a signed payment. [See what changed β†’](https://asterpay.io/try/) [API docs](https://x402.asterpay.io/docs) [AsterPay](/) Β· [Blog](/blog/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # How an AI Agent Finds a Merchant's Verified IBAN | AsterPay Blog Source: Markdown mirror: > An AI agent knows the company but not the IBAN. AsterPay [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / Merchant IBAN Resolution # How an AI Agent Finds a Merchant's Verified IBAN An agent knows who it wants to pay, but not where. AsterPay's Merchant Payment Endpoint turns that business identity into a verified IBAN, resolved from provable sources, with provenance and Verification of Payee, ready for SEPA Instant. June 16, 2026 4 min read By Petteri, AsterPay Agent payment protocols like x402 assume the agent already holds a recipient address. Real commerce does not work that way. An agent processing an invoice, restocking inventory, or paying a supplier starts from a business identity : a legal name, a VAT number, a registry entry. Turning that identity into a payable bank account, reliably, is the job of the Merchant Payment Endpoint. AsterPay solves it the watertight way: a payee's IBAN is resolved only from sources that can be proven , each one tagged with where it came from and how strongly it is backed. The agent always knows the origin of the account it is about to pay. ## Every IBAN comes from a provable source AsterPay's Merchant Payment Endpoint (MPE) returns a payee's IBAN only when it came from a source that can be proven, and every result carries that source with it. There are three provable sources, in descending order of strength: - Verified merchant registry β€” a merchant that onboarded and proved control of the account. - Signed payment manifest β€” the merchant's own `/.well-known/pay.json`, published under their domain. - Structured e-invoice β€” the IBAN read directly out of an EN16931 invoice (UBL or CII / ZUGFeRD), field BT-84, from the document the merchant themselves issued. Provenance is part of the answer. Every resolved IBAN carries a logged provenance and a confidence level: `verified`, `document`, or `asserted`. The agent does not just learn the IBAN, it learns how strongly that IBAN is backed, and can decide accordingly. ## Then it gets verified Resolution is only half the job. Every resolved IBAN passes full structure and checksum validation, and every API response states the verification method used (`vop_method`), so the agent always knows exactly which checks have run. The strongest check is bank-side Verification of Payee (VoP) , the EU-mandated name match that banks must offer on euro payments since October 2025. It confirms the account belongs to the named beneficiary. AsterPay runs VoP through its licensed settlement partner at payout; until that partner check runs, the response reports its status honestly (checksum validated, source provenance verified) and never claims a name match it has not performed. Why it is reliable by default. Every IBAN comes from a provable source, carries provenance and a confidence level, and is structurally validated, with bank-side name matching run through a licensed partner at payout. An agent can pay a company it has never seen, day or night, knowing exactly where the money is going and which checks have run. ## What it looks like in one call Resolution is free. Try the public demo merchant: ``` GET /v1/mpe/merchants/resolve?business_id=FI-DEMO-0001&business_id_type=demo { "merchant_id": "mpe-demo-0001", "name": "Demo Merchant Oy", "country": "FI", "verified": true, "payment_endpoints": [{ "type": "iban", "currency": "EUR", "method": "sepa_instant", "iban_last4": "1234", "bic": "NDEAFIHH", "provenance": "signed_pay_manifest", "confidence": "verified", "iban_checksum": "valid", "vop": { "performed": false, "status": "bank_vop_pending_partner_rollout" } }], "policy": { "auto_pay_allowed": false, "reason": "demo merchant only" } } ``` Each endpoint carries its provenance , a confidence level , the checksum result, and an honest VoP status β€” so the agent knows exactly which checks have run before it pays. `POST /v1/mpe/settle` then chains the full pipeline β€” resolve, payee validation, the paying agent's trust check, USDC/EURC-to-EUR conversion, and SEPA Instant payout β€” in a single call. The full specification, response fields, and confidence model are in our learn guide. ### The Merchant Payment Endpoint, in detail Full specs: provable sources, the provenance and confidence model, validation, and Verification of Payee. [Read the full spec](/learn/merchant-payment-endpoint/) [Create a free account](https://app.asterpay.io/signup) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # AsterPay Blog β€” AI Agent Payments, x402, USDC to EUR, Stablecoin Off-Ramp Source: Markdown mirror: > Technical articles on AI agent payments, the x402 protocol, USDC-to-EUR settlement, stablecoin off-ramps, and building agentic commerce in Europe. By the AsterPay team. [AsterPay](/) [Home](/) # Blog Technical guides on AI agent payments, stablecoin settlement, and agentic commerce infrastructure. [Engineering ## First Call Free: What Weeks of 402 Telemetry Taught Us About Agent Conversion Agents discovered our API around the clock and paid almost never. The rail worked; the offer didn't. Four funnel fixes: free EUR estimates, first call free per wallet, example responses inside every 402, and a paid agent-readiness endpoint. July 4, 2026 5 min read](/blog/first-call-free) [Technical ## Agent Constitutions: Proving What an AI Agent Promised Identity is who an agent is. Reputation is what others think. Neither tells you what it committed to. A small, verifiable mechanism: canonical-hash an agent's payment policy and commit it on-chain to ERC-8004. June 27, 2026 4 min read](/blog/agent-constitution) [Perspective ## The Agentic Discovery Layer Has Two Floors Winning AI visibility gets an agent to your door. The floor below decides whether it can actually pay you, and whether you should let it: payment discovery, trust, and settlement. June 23, 2026 5 min read](/blog/agentic-discovery-two-floors) [Engineering ## How an AI Agent Finds a Merchant's Verified IBAN AsterPay's Merchant Payment Endpoint turns a company name into a verified IBAN, resolved from provable sources, with logged provenance and a disclosed Verification of Payee method. June 16, 2026 4 min read](/blog/how-agents-find-merchant-iban) [Industry ## AWS Just Added x402 Monetization. What EU Publishers Do With the USDC AWS WAF can now charge AI bots via x402 and pay out in stablecoins. But the money lands as USDC on a wallet, not EUR in a bank. Here is how European publishers close that last mile. June 16, 2026 4 min read](/blog/aws-x402-monetization-eur-payout) [Perspective ## MiCA's 1 July Deadline: Who Actually Survives Only ~200 of 1,200+ EU crypto firms are licensed. The deadline is not filtering for size or brand, it is filtering for compliance and custody. Why non-custodial barely feels it. June 15, 2026 4 min read](/blog/mica-deadline-who-survives) [Perspective ## Settlement Is Becoming a Commodity. Trust Is the Asset. When the buyer is a software agent, moving money gets cheap and abundant. The scarce asset is a portable, owned record of which agents have behaved well, the trust layer, not the rail. June 14, 2026 6 min read](/blog/trust-is-the-asset) [Industry ## Coinbase Commerce Is Shutting Down. What Now? Coinbase Commerce stops serving non-US merchants on March 31. If you're a European business accepting crypto β€” or building for AI agents β€” here are your options. March 26, 2026 5 min read](/blog/coinbase-commerce-shutdown) [Guide ## How to Convert USDC to EUR via SEPA Instant in 2026 A practical guide for developers, merchants, and AI agents who need to settle USDC, EURC, or EURCV stablecoins into euros β€” fast, compliant, and at low cost. March 15, 2026 8 min read](/blog/usdc-to-eur-settlement) [Protocol ## What Is the x402 Payment Protocol? The protocol that turns HTTP 402 "Payment Required" into reality β€” letting AI agents pay for API calls with USDC, natively built into the web. March 15, 2026 7 min read](/blog/x402-payment-protocol) [Industry ## AI Agent Payments in Europe: MiCA, SEPA Instant, and Agentic Commerce Autonomous AI agents are starting to transact billions. In Europe, they need MiCA-aligned partner routing, SEPA Instant settlement, and proper identity. Here's the stack. March 15, 2026 9 min read](/blog/ai-agent-payments-europe) [Developer ## Stablecoin Off-Ramp API for Developers Convert USDC, EURC, and EURCV to EUR via SEPA Instant. Multi-chain, MiCA-aligned via licensed partners, and designed for both human developers and autonomous AI agents. March 15, 2026 6 min read](/blog/stablecoin-offramp-api) Also publishing on [Paragraph (Web3 Blog) β†’](https://paragraph.com/@asterpay) [AsterPay](/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # MiCA's 1 July Deadline: Who Actually Survives | AsterPay Blog Source: Markdown mirror: > The MiCA transition ends 1 July 2026 and only ~200 of 1,200+ firms are licensed. The survivors are the compliant and the non-custodial. A short read on what the deadline really filters for. [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / MiCA Deadline # MiCA's 1 July Deadline: Who Actually Survives The transition period ends in two weeks. Around 200 of 1,200+ firms are licensed. The deadline is not really filtering for size or brand. It is filtering for two things: compliance and custody. June 15, 2026 4 min read By Petteri, AsterPay On 1 July 2026 the MiCA transitional period ends across the entire EU. After that date, any firm providing crypto-asset services to EU clients without a CASP authorization is in breach of EU law and has to cease or wind down. ESMA has confirmed there are no further extensions. The headline number is stark. As of May 2026, roughly 200 entities held a full MiCA licence, out of more than 1,200 legacy registrations, against a pre-MiCA population estimated at 3,000. That is a conversion rate around 17%. Most firms that operated in Europe under old national regimes will not be authorized when the clock runs out. ## The deadline filters for two things It is tempting to read this as big-versus-small, but that is not what is happening. The deadline filters for compliance and custody . Compliance is obvious: you either hold the authorization, or you have a credible application filed before your national deadline, or you are out. The less obvious one is custody, and it is where most of the pain lands. The detail most coverage misses: a MiCA authorization covers one specific legal entity, not the group. You cannot lean on an affiliate's licence, and custodial services cannot be outsourced to an unlicensed entity, even inside the same group. A lot of "we're covered" claims do not survive that test. ## Non-custodial barely feels it If you never hold client funds, there is no custody to license and nothing to wind down. The firms in genuine trouble are the custodial ones that assumed the grace period would stretch. The firms that are calm are the ones where the regulated activity already sits with an authorized entity. This is the structural choice that matters. A non-custodial design routes the regulated steps, custody and the stablecoin-to-fiat conversion, through a licensed partner. The technology layer on top never touches the funds, so it is not the thing being regulated. There is no scramble, because there was never anything to scramble. ## The assets got filtered too MiCA does not only sort firms, it sorts stablecoins. USDC and EURC are authorized MiCA-compliant e-money tokens. USDT declined authorization and has been pulled from EU-regulated venues. The whitelist of acceptable assets is becoming an enforcement mechanism in its own right. For anyone building settlement, the implication is direct: build on the compliant assets, because the venues you depend on can only list those. Where AsterPay sits. We are non-custodial: we never hold funds. Custody and the USDC/EURC-to-EUR conversion run through a licensed EU partner, so the regulated activity always sits with an authorized entity. Agent and merchant payments settle to EUR via SEPA Instant, MiCA-aligned, with the Travel Rule automated. Compliant by design, not by deadline. ## What to do before 1 July - Identify which legal entity performs each regulated step, and confirm it is on the ESMA Interim MiCA Register. - Make sure custody and conversion run through a licensed CASP, not an unlicensed group affiliate. - Move off non-compliant stablecoins toward USDC and EURC. - If you are unauthorized, execute a wind-down or migrate clients to a licensed provider before the deadline. The deeper breakdown, including the five options for unlicensed firms and what it means specifically for agent payments and crypto APIs, is in our learn guide. ### What the deadline means for agent payments The full guide: numbers, options, and the non-custodial structure that stays compliant. [Read the guide](/learn/mica-deadline-2026-agent-payments/) [Create a free account](https://app.asterpay.io/signup) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # Stablecoin Off-Ramp API for Developers β€” USDC/EURC to EUR in Seconds | AsterPay Source: Markdown mirror: > Integrate a stablecoin off-ramp API in minutes. Convert USDC, EURC, and EURCV to EUR via SEPA Instant. Multi-chain support (Base, Ethereum, Solana). MiCA-aligned via licensed partners. For developers and AI agents. [AsterPay](/) [All Articles](/blog/) [Home](/) / [Blog](/blog/) / Stablecoin Off-Ramp API # Stablecoin Off-Ramp API for Developers Convert USDC, EURC, and EURCV to EUR via SEPA Instant. Multi-chain, MiCA-aligned via licensed partners, and designed for both human developers and autonomous AI agents. Published March 15, 2026 6 min read By AsterPay Building an app that handles stablecoins? At some point, you or your users need to convert those USDC tokens to actual euros in a bank account. That's what an off-ramp API does β€” and in 2026, it's easier than ever. ## What Is a Stablecoin Off-Ramp? An off-ramp converts crypto assets (in this case, stablecoins like USDC, EURC, or EURCV) into EUR currency (EUR) and deposits it to a bank account. The "API" part means you can integrate this conversion directly into your application without sending users to an exchange. #### On-Ramp EUR (bank) β†’ USDC (blockchain). User buys stablecoins. #### Off-Ramp USDC (blockchain) β†’ EUR (bank). User sells stablecoins to EUR. ## Why You Need an Off-Ramp API in 2026 - AI agent payments : Your agent earns USDC via x402 β€” you need those earnings in EUR - Merchant acceptance : Accept crypto from customers, receive EUR in your business account - Payroll and payouts : Convert stablecoin treasury to EUR for salaries and expenses - DeFi exits : Move yield farming profits from on-chain to your bank - Remittances : Send USDC internationally, recipient gets local EUR ## AsterPay Off-Ramp API: Quick Start ### Step 1: Get a Settlement Estimate ``` curl https://x402.asterpay.io/v1/settlement/estimate \ -H "Content-Type: application/json" \ -d '{ "amount": "500", "currency": "USDC", "target": "EUR", "chain": "base" }' ``` ### Step 2: Python Integration ``` from asterpay import AsterPay client = AsterPay() # Get real-time estimate estimate = client.settlement.estimate( amount="500", currency="USDC", target="EUR", chain="base" ) print(f"Receive: €{estimate.estimated_eur}") print(f"Fee: {estimate.fee_percent}") print(f"Time: {estimate.settlement_time}") ``` ### Step 3: MCP Server (For AI Agents) ``` // claude_desktop_config.json { "mcpServers": { "asterpay": { "command": "npx", "args": ["@asterpay/mcp-server"] } } } // Your AI agent can now call: // - get-settlement-estimate // - check-trust-score // - get-market-price // All via x402 micropayments ``` ## Supported Assets and Chains | | Asset | Chains | Target | Speed | USDC | Base, Ethereum, Solana, Polygon, XRPL | EUR | <10s | EURC | Base, Ethereum | EUR | <10s | EURCV | Ethereum | EUR | <10s ## Off-Ramp API Comparison: 2026 | | Feature | AsterPay | Generic stablecoin offramp API | Circle | Exchange APIs | Settlement Speed | <10s SEPA Instant | 1-2 days | 1-2 days | 1-3 days | AI Agent Native | Yes (x402, MCP) | No | No | No | Multi-chain | 6+ chains | Limited | Ethereum, Solana | Varies | No Signup (read) | Yes | No | No | No | MiCA Compliant | Yes | Yes | Yes | Varies | KYA (Agent ID) | Yes | No | No | No ## Compliance Built In Every off-ramp transaction through AsterPay is automatically checked for: - Sanctions β€” OFAC, EU, UN lists via Chainalysis (<100ms) - MiCA-aligned partner routing β€” EU regulatory framework for stablecoin operations - Travel Rule β€” automated for transactions over €1,000 - Source of funds β€” wallet history analysis for risk scoring Unique to AsterPay: Our "Know Your Agent" framework gives AI agents a Trust Score (0-100). Higher-scoring agents get higher transaction limits β€” like a credit score for machines. ## Pricing - Developer / agent API access : $0.001–$0.10 USDC per call via x402 or MPP (per-endpoint, typical $0.01). Sandbox free up to 1,000 calls/day. No signup. - Merchant EUR settlement : 0.5% + €0.10 per settled transaction, all-in. Volume discounts from €50k/month. - Enterprise (>€500k/month): negotiated pricing, SLA and dedicated support. ## Get Started ``` # Option 1: Python pip install asterpay # Option 2: MCP Server npx @asterpay/mcp-server # Option 3: Direct API curl https://x402.asterpay.io/v1/settlement/estimate \ -d '{"amount":"100","currency":"USDC","target":"EUR"}' ``` ### Integrate Stablecoin Off-Ramp Today USDC to EUR in under 10 seconds. Multi-chain. MiCA-aligned via licensed partners. Agent-native. [Create Free Account](https://app.asterpay.io/signup) [API Docs](/docs/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # Settlement Is Becoming a Commodity. Trust Is the Asset. | AsterPay Blog Source: Markdown mirror: > In the agent economy, moving value is becoming instant and near-free. The scarce asset is trust: a portable, owned record of which agents have behaved well. Why the trust layer, not the rail, is the real moat. [AsterPay](/) [All posts](/blog/) [Blog](/blog/) / Trust Is the Asset # Settlement Is Becoming a Commodity. Trust Is the Asset. When the buyer is no longer a person, moving money gets faster, cheaper, and more abundant. The scarce thing is no longer the movement. It is the confidence to let the movement happen at all. June 14, 2026 6 min read By Petteri Leinonen, Founder, AsterPay I've been thinking a lot about what commerce looks like when the buyer is no longer a person. For the entire history of payments, software has been a tool that humans used to move money. A person decided, and a system executed. We are now crossing into something different. For the first time, software agents are becoming economic counterparties in their own right. They discover services, negotiate, pay, and get paid, often without a human in the loop for any single transaction. That is a mind-bender, because it changes the most basic question in commerce: who, or what, am I actually transacting with? What is at stake is not a faster rail or a cheaper stablecoin. It is how value moves and how trust is established in a world where the actors initiating payments are autonomous, numerous, and increasingly capable. Get the rail right and you have moved money. Get the trust right and you have built something that lasts. ## Two kinds of capital: settlement and trust Every business operating in the agent economy is going to have to build two things. Call them settlement capital and trust capital. Settlement capital is the ability to move value with finality, to turn a stablecoin payment from an agent into euros in a merchant's account, irreversibly, in seconds. Trust capital is the accumulated, owned record of which agents have behaved well: who they act for, what they are authorized to do, and how they have performed across every transaction they have ever settled. ## Why trust gets more valuable as settlement gets cheaper Here is the part that matters. As settlement gets faster, cheaper, and more abundant, trust capital does not become less valuable. It becomes more valuable. Settlement is on a path to commodity. The moment value can move instantly and at near-zero cost between any two parties, the scarce thing is no longer the movement. It is the confidence to let the movement happen at all. Without trust, you have compute with a wallet, transacting in circles. You can route a transaction through any rail. But an agent can never offload the trust it has earned. This means the real opportunity is not in picking the best rail or the cheapest network. It is in building a trust loop on top of settlement, where every payment makes the next one safer. You can swap one stablecoin for another, one chain for another, one settlement provider for another. But an agent can never offload the trust it has earned. Reputation is the one thing in this system that cannot be re-issued on demand. ## Trust has to be portable, or you never owned it This requires an architecture where trust lives in the open and belongs to the parties who built it, not locked inside a single closed network that can rent it back to you. An attestation that an agent is who it claims to be, acts for whom it claims to act, and has settled honestly a thousand times should be portable. A merchant should be able to switch out the model behind its agent, or the provider behind its settlement, without losing the reputation those agents have accumulated. That portability is the real test of sovereignty in the era ahead. If your trust evaporates the moment you change vendors, you never owned it. ## Turning behavior into verifiable signal Concretely, this means turning behavior into queryable, verifiable signal. On-chain attestations that capture real history rather than self-declared claims. A Know Your Agent layer that scores an agent on what it has actually done, not on who vouched for it. Trust that grows stronger on real traces from inside the network, and a reputation graph that any counterparty can check before it accepts a payment. This is what KYA is for. Know Your Agent extends KYC and KYB to autonomous software: verify identity (ERC-8004), screen for sanctions, and score behavior into a single number a counterparty can act on before money moves. [How KYA works in Europe.](/learn/know-your-agent-compliance-eu/) ## The compounding trust graph This loop becomes the new IP of the agent economy. I think of it as a compounding trust graph, and unlike most assets, it gets harder to replicate the longer it runs. Every honest settlement produces a better trust signal, which makes the next decision sharper, which attracts more good agents, which produces more signal. The networks that build this early will have an advantage that no individual model capability erases, because the asset is not the model. It is the accumulated, owned history. ## Open, not enclosed The last thing any of us should want is a world where a handful of closed networks own the identity and reputation of every agent, and rent that trust back to everyone else. We have seen what concentration does. The first era of digital payments routed the world's commerce through a very small number of gatekeepers, and the value, and the leverage, concentrated accordingly. The agent economy is being built right now. We get to choose whether its trust layer is open or enclosed. There is no societal permission for an agent future in which a few intermediaries sit between every machine and every euro. The political economy will not tolerate it, and frankly it would be bad architecture. Trust that everyone depends on should be a commons that everyone can build on, not a toll booth. So our priority has to be a frontier ecosystem for agent commerce, not just a frontier rail. One where settlement is open and non-custodial, where the network moves value without ever holding it, and where trust is built on open standards that any business can read, write to, and own. One where value flows broadly: to the agents that behave well, the merchants that get paid in real money with real finality, and the markets around them. This is the ethos I have grown up with in this industry. Platforms should enable more value on top than they capture inside. Settlement should be a utility, not a landlord. Trust should belong to the firms that earned it. ## What we are building When that happens, the agent economy compounds for everyone in it. Merchants get paid instantly in euros. Agents earn reputations they carry with them. Businesses own the trust loop that encodes how their agents behave, and that loop gets more valuable every day it runs. That is the stable equilibrium we should build together. Not a few networks that eat everything they touch, but an open settlement layer and an owned trust layer, compounding side by side. This is the thesis behind AsterPay. Non-custodial EUR settlement via SEPA Instant for the rail, and an open Know Your Agent trust layer (ERC-8004 identity, sanctions screening, a 0-100 trust score) for the asset. We never hold the funds, and the trust an agent earns stays portable. ### Build on the open trust layer Free trust scoring, no signup. Score any agent wallet before you accept its payment. [How KYA works](/learn/know-your-agent-compliance-eu/) [How agents pay merchants](/learn/how-ai-agents-pay-merchants/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # How to Convert USDC to EUR via SEPA Instant β€” Complete Guide 2026 | AsterPay Source: Markdown mirror: > Convert USDC to EUR in under 10 seconds using SEPA Instant. Step-by-step guide for developers and AI agents. No signup required. Supports Base, Ethereum, Solana, and XRPL. [AsterPay](/) [All Articles](/blog/) [Home](/) / [Blog](/blog/) / USDC to EUR Settlement # How to Convert USDC to EUR via SEPA Instant in 2026 A practical guide for developers, merchants, and AI agents who need to settle USDC, EURC, or EURCV stablecoins into euros β€” fast, compliant, and at low cost. Published March 15, 2026 8 min read By AsterPay As stablecoins go mainstream in Europe β€” USDC surpassed $81 billion in market cap, and EURC adoption is accelerating under MiCA β€” the question for every developer, merchant, and AI agent operator is the same: how do I turn these digital dollars and euros into real euros in my bank account? The answer in 2026 is SEPA Instant settlement . With the right API, you can convert USDC or EURC to EUR and have it in your IBAN in under 10 seconds. Here's exactly how. ## Why USDC-to-EUR Matters Now Three things changed in 2025-2026 that make stablecoin-to-EUR settlement critical infrastructure: - MiCA regulation took effect β€” European merchants and platforms can now legally accept stablecoins if they use compliant off-ramp providers. - SEPA Instant became mandatory β€” All EU banks must support instant euro transfers, making real-time settlement possible. - AI agents started transacting β€” The x402 payment protocol (by Coinbase) enabled AI agents to pay for API calls with USDC. Those USDC payments need to be converted to EUR for European businesses. ## Method 1: API Integration (For Developers) If you're building an app or operating AI agents that receive USDC payments, the fastest path is a settlement API. ### Using AsterPay's Settlement API ``` # Check settlement estimate (no auth required) curl https://x402.asterpay.io/v1/settlement/estimate \ -H "Content-Type: application/json" \ -d '{"amount": "100", "currency": "USDC", "target": "EUR"}' # Response: { "estimatedEur": "92.45", "fee": "0.50", "feePercent": "0.5%", "settlementTime": " Key features of this approach: - No signup required for read-only endpoints (trust scores, estimates, market data) - x402 protocol support β€” your AI agent can pay for API calls directly with USDC - Multi-chain β€” accepts USDC from Base, Ethereum, Solana, XRPL, Polygon - SEPA Instant β€” EUR arrives in your bank account in <10 seconds ### Using the MCP Server (For AI Agents) If you run AI agents in Claude, Cursor, or any MCP-compatible environment: ``` # Add to your MCP config β€” that's it { "mcpServers": { "asterpay": { "command": "npx", "args": ["@asterpay/mcp-server"] } } } ``` Your AI agent can then call tools like `get-settlement-estimate`, `check-trust-score`, and `get-market-price` β€” paying per call via x402. ### Using the Python SDK ``` pip install asterpay from asterpay import AsterPay client = AsterPay() estimate = client.settlement.estimate( amount="100", currency="USDC", target="EUR" ) print(f"You'll receive €{estimate.estimated_eur}") ``` ## Method 2: Merchant Settlement (For Businesses) If you're a merchant accepting stablecoin payments and want EUR in your bank: - Apply at [asterpay.io/partners](https://asterpay.io/partners/) - KYC/KYB verification (1-2 business days) - Test in sandbox with test USDC and a test IBAN - Go live β€” receive real EUR to your business IBAN Settlement fees are competitive with volume discounts. SEPA Instant means you're not waiting days for your money. ## Supported Stablecoins and Chains | | Stablecoin | Chains | Settlement | USDC | Base, Ethereum, Solana, Polygon, XRPL | EUR via SEPA Instant | EURC | Base, Ethereum | EUR via SEPA Instant | EURCV | Ethereum | EUR via SEPA Instant ## Compliance: MiCA, Sanctions, and Travel Rule Any serious stablecoin-to-EUR solution must handle compliance. Here's what AsterPay covers: - MiCA-aligned via licensed partners β€” EU-native entity (Cyprus), licensed settlement partners - Sanctions screening β€” Every transaction checked against OFAC, EU, and UN lists via Chainalysis in <100ms - Travel Rule β€” Automated for transactions over €1,000 - Agent identity β€” ERC-8004 on-chain identity for AI agents, Trust Score 0-100 For AI agent developers: AsterPay's "Know Your Agent" (KYA) framework means your agent gets a Trust Score. Higher trust = higher transaction limits. This is unique to AsterPay β€” traditional off-ramps don't understand agent identity. ## Cost Comparison: USDC-to-EUR Off-Ramps in 2026 | | Provider | Fee | Settlement Time | Agent Support | AsterPay | Competitive | <10 seconds | Native (x402, MCP, KYA) | Exchange (manual) | 0.1-0.5% | 1-3 business days | None | Generic stablecoin offramp API | Varies | 1-2 business days | Limited | Circle Redeem | Free (min $100K) | 1-2 business days | None ## Getting Started Today The fastest way to start: - Check a settlement estimate β€” hit the API, no signup needed - Install the MCP server β€” `npx @asterpay/mcp-server` - Or use Python β€” `pip install asterpay` - For merchant settlement β€” [apply here](https://asterpay.io/partners/) ### Start Converting USDC to EUR No signup required for read-only API. Full settlement in <10 seconds. [Create Free Account](https://app.asterpay.io/signup) [Try API (No Signup)](/docs/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # What Is the x402 Payment Protocol? How AI Agents Pay for APIs | AsterPay Source: Markdown mirror: > The x402 payment protocol lets AI agents pay for API calls with USDC, built into HTTP. Learn how x402 works, how to accept x402 payments, and how to settle them to EUR. [AsterPay](/) [All Articles](/blog/) [Home](/) / [Blog](/blog/) / x402 Payment Protocol # What Is the x402 Payment Protocol? The protocol that turns HTTP 402 "Payment Required" into reality β€” letting AI agents pay for API calls with USDC, natively built into the web. Published March 15, 2026 7 min read By AsterPay For decades, the HTTP status code `402 Payment Required` was "reserved for future use." In 2025, Coinbase shipped the future: the x402 payment protocol , which lets any HTTP endpoint require a USDC payment before returning data. This is the protocol powering the AI agent economy. Here's everything you need to know. ## How x402 Works: The 60-Second Explanation - An AI agent makes an HTTP request to an API endpoint - The server responds with `HTTP 402` and a payment requirement (e.g., "0.004 USDC on Base") - The agent's wallet signs a USDC transaction - A facilitator (like AsterPay) verifies the payment and settles it - The server returns the actual data The entire flow happens in milliseconds. No API keys, no subscriptions, no invoices. Just pay-per-call. ``` # A real x402 request flow: # 1. Agent makes request GET /v1/market/price/BTC HTTP/1.1 Host: x402.asterpay.io # 2. Server responds with 402 + payment details HTTP/1.1 402 Payment Required X-Payment: {"amount": "0.004", "currency": "USDC", "chain": "base"} # 3. Agent pays and retries GET /v1/market/price/BTC HTTP/1.1 X-Payment-Proof: {signed_transaction} # 4. Server delivers data HTTP/1.1 200 OK {"price": "67234.50", "currency": "USD", ...} ``` ## Why x402 Matters for AI Agents Traditional payment methods (Stripe, invoices, subscriptions) require a human in the loop. An AI agent can't fill out a Stripe checkout form. x402 solves this by making payments machine-native : - No signup β€” the agent just needs a wallet with USDC - No API keys β€” payment IS the authentication - Micropayments β€” pay $0.001 per call, not $99/month - Instant β€” no waiting for payment confirmation - Composable β€” agents can chain API calls across multiple providers The x402 ecosystem is growing fast. The [x402 Foundation](https://x402.org/ecosystem) now spans payment networks, cloud platforms and crypto-native teams, with services discoverable through directories like x402scan. AsterPay is the only provider offering EUR settlement via SEPA Instant for x402 payments in Europe. ## x402 vs. Google AP2 vs. Traditional Payments x402 isn't the only agent payment protocol. Google recently launched AP2 (Agent Payments Protocol) . Here's how they compare: - x402 : Built on HTTP, uses USDC on-chain, fully decentralized. Best for: developer APIs, AI agent tools, micropayments. - AP2 : Google's approach, designed for agent-to-business commerce. Integrates with Google's AI ecosystem. Best for: commercial transactions, booking, purchasing. - Traditional (Stripe/cards) : Requires human authentication. Not suitable for autonomous agents. AsterPay supports both x402 and AP2, giving your agents maximum interoperability. ## How to Accept x402 Payments If you're an API provider and want to monetize with x402: ### Option 1: Use AsterPay as Your Facilitator ``` // In your Express/Fastify/Next.js API: import { x402Middleware } from '@asterpay/x402-sdk'; app.use('/v1/*', x402Middleware({ facilitator: 'https://x402.asterpay.io', price: '0.004', // USDC per call currency: 'USDC', chain: 'base' })); ``` AsterPay handles payment verification, settlement, and compliance. You receive EUR via SEPA Instant. ### Option 2: Self-Host x402 is an open protocol. You can run your own facilitator, but you'll need to handle settlement, compliance, and multi-chain support yourself. ## The EUR Settlement Gap Here's the challenge most x402 providers don't solve: your AI agent pays in USDC on Base, but you β€” the European merchant or developer β€” want euros in your bank account . AsterPay bridges this gap. Every USDC payment that flows through our facilitator can be automatically settled to EUR via SEPA Instant. No manual conversion, no exchange accounts, no delays. AsterPay is a European x402 facilitator offering EUR settlement via SEPA Instant. (x402 became a Linux Foundation project in 2026; its public ecosystem page moved to a membership model.) ## Get Started with x402 - For AI agent developers : Install `npx @asterpay/mcp-server` or `pip install asterpay` - For API providers : Add x402 middleware to your endpoints β€” [see docs](/docs/) - For merchants : [Apply for EUR settlement](/partners/) ### Join the x402 Economy The AI agent payment revolution is here. Start accepting or making x402 payments today. [Create Free Account](https://app.asterpay.io/signup) [Read the Docs](/docs/) [AsterPay](/) Β· [Blog](/blog/) Β· [Docs](/docs/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # /budget β€” Give your AI agent a budget, not your wallet | AsterPay Source: Markdown mirror: > One USDC transfer gives your agent a hard spending cap across every paid AsterPay API. No API keys, no card on file, no KYC. Sanctions-screened, on-chain verified. Set up in one line: claude mcp add asterpay -- npx -y @asterpay/mcp-server [AsterPay /budget](/) [How it works](#how) [API](#api) [GitHub](https://github.com/aelira-labs) [Get started](#get-started) Live on Base mainnet Β· USDC # Give your agent /budget, not your wallet. One USDC transfer gives your agent a hard spending cap across every paid AsterPay API. It spends per call until the budget runs out β€” then it stops. No API keys. No card on file. No surprise bills. $ `claude mcp add asterpay -- npx -y @asterpay/mcp-server` [See how it works β†’](#how) [Live API endpoint](https://x402.asterpay.io/v1/budget/info) claude β€” agent session (simulated demo) BUDGET ACTIVE Remaining $10.000 0 calls How it works ## Fund once.The agent does the rest. No signup forms, no dashboards to babysit. The budget is the product β€” a prepaid balance with a cryptographic leash. 01 β€” HUMAN ### Send USDC once You (the human) send 1–500 USDC to AsterPay on Base. One transfer from any wallet β€” Coinbase, MetaMask, Rabby, anything. An agent can never grant itself money. 02 β€” AGENT ### Run `/budget` The agent activates the budget through the AsterPay MCP server and gets a token. Every paid call β€” research, code review, token analysis β€” deducts its exact price from the balance. Credited `1:1`, no platform fee, valid for `90 days`. 03 β€” HARD CAP ### It stops at zero Balance exhausted β†’ the API answers `402` and the agent stops gracefully. Not a soft warning. Not a "we'll bill you later." The money simply isn't there to spend. Why it's different ## A spending limit thatisn't a promise. β›” ### Hard cap, enforced server-side Atomic balance deduction per call. Two concurrent calls can never overspend the same dollar β€” guaranteed at the database level, not in agent code. πŸ›‘οΈ ### Sanctions-screened by default Every funding wallet is screened against the Chainalysis Sanctions Oracle β€” the public on-chain contract covering OFAC, EU and UN designations β€” before a budget is issued. Verifiable on Basescan, screened at the rail, not bolted on. πŸ”‘ ### No API keys, no card Nothing to leak, nothing to rotate, no card-on-file for an AI to max out. The budget token is scoped to spending the prepaid balance β€” and nothing else. 🧾 ### Every call receipted Per-call spend log with endpoint, price, and timestamp. `get_budget_status` shows exactly where every cent went. ⚑ ### Works where agents live Native slash command in Claude Code, tools in Cursor and any MCP client. Every paid AsterPay API works instantly β€” token analysis, wallet scores, code review, deep KYA. πŸ‡ͺπŸ‡Ί ### EUR settlement underneath Built on the only EUR-native x402 facilitator. When your agent needs to pay a real European business, the same rail settles to IBAN via SEPA Instant. ### "Do I need KYC for this?" No. A prepaid budget is crypto in, API calls out β€” no fiat payout, no custody of customer funds, no card issuing. So there is no KYC, no KYB, no signup form . What you get instead is KYA β€” Know Your Agent. The funding wallet is sanctions-screened at creation, the payment is verified on-chain, and the budget can only be created by a human transfer. Compliance is in the rail, not in a form. βœ• KYC β€” not required No identity documents. Fund from any wallet. βœ• KYB β€” not required Only needed later if you settle EUR to an IBAN. βœ“ KYA β€” built in Chainalysis sanctions oracle screens every funding wallet. βœ“ On-chain verification Deposit tx verified (recipient, amount, sender) before credit. βœ“ 90-day validity Budgets expire 90 days after funding. Unused balance? DM [@Asterpayment](https://twitter.com/Asterpayment) before expiry and we roll it into a fresh budget. For builders ## Two endpoints.That's the whole API. Skip the MCP server if you want β€” the raw HTTP API is just as simple. Budgets work on every paid AsterPay endpoint via one header. POST /v1/budget/create x402.asterpay.io ``` # 1. Send USDC on Base (you choose the amount, 1–500) # 2. Redeem the tx for a budget token: curl -X POST https://x402.asterpay.io/v1/budget/create \ -H "Content-Type: application/json" \ -d '{ "amountUsd": 10, "txHash": "0xabc…", "wallet": "0xYourWallet" }' β†’ { "budget": { "token": "bud_…", "balanceUsd": 10 } } ``` GET any paid endpoint one header ``` # Spend from the budget on any paid AsterPay endpoint: curl https://x402.asterpay.io/v1/crypto/token-analysis/0x… \ -H "X-Budget-Token: bud_…" β†’ 200 OK Β· X-Budget-Remaining: 9.900000 # When the balance hits zero: β†’ 402 { "error": "Budget balance too low…", "topUp": { … } } ``` ## Your agent is readyto earn its allowance. One line in your terminal. One transfer. Done. (Cursor and other MCP clients: add `npx -y @asterpay/mcp-server` to your MCP config.) $ `claude mcp add asterpay -- npx -y @asterpay/mcp-server` Questions? [Read the live API spec](https://x402.asterpay.io/v1/budget/info) or DM [@Asterpayment](https://twitter.com/Asterpayment) Β© 2026 AELIRA LTD Β· AsterPay β€” EUR settlement for AI agent commerce [asterpay.io](/) [Docs](/docs) [KYA](/trust/) [X](https://twitter.com/Asterpayment) --- # AsterPay vs Coinbase CDP β€” honest comparison for x402 facilitators | AsterPay Source: Markdown mirror: > AsterPay vs Coinbase CDP (Developer Platform): canonical x402 facilitator on Base vs EU-native facilitator with EUR settlement, KYA trust and dual x402+MPP. Complementary roles in the agent payments stack. [← All comparisons](/compare/) # AsterPay vs Coinbase CDP β€” honest comparison Updated 3 May 2026 Β· 6 minute read Β· By Petteri, Co-founder Short answer Coinbase Developer Platform (CDP) is the canonical x402 facilitator. AsterPay is the EU-native facilitator that adds EUR settlement, KYA trust scoring and dual x402+MPP support on top. The two are not in head-to-head competition: CDP runs the reference facilitator on Base for USDC-in-USDC-out flows; AsterPay runs an EU-licensed facilitator for USDC-in-EUR-out flows. Most production stacks will use one or both depending on the merchant geography and settlement currency. ## What each one is Coinbase Developer Platform (CDP) , launched by Coinbase in 2024, is a developer infrastructure platform that includes a wallet API, RPC nodes, smart-contract tooling and the canonical x402 facilitator. CDP's x402 facilitator is the reference implementation: it verifies payment proofs, executes settlements on Base, and is the default endpoint that every x402-aware agent SDK ships with. CDP also operates Coinbase's broader exchange and custody businesses under US state and federal regulation. AsterPay , operated by AELIRA LTD (Cyprus), is an EU-native x402 facilitator that adds EUR settlement via SEPA Instant, KYA trust scoring on the agent wallet, dual x402+MPP support on every paid endpoint, and multi-chain ingress (Base, Polygon, Arbitrum, Optimism, Ethereum, Solana). AsterPay is listed on the official x402 ecosystem page maintained by Coinbase and is operationally complementary to CDP's facilitator. ## Side-by-side comparison | | Capability | Coinbase CDP facilitator | AsterPay facilitator | Role | Canonical x402 reference facilitator | EU-native EUR settlement facilitator | Settlement currency out | USDC (stays on-chain) | EUR via SEPA Instant (and USDC if merchant prefers) | Regulatory home | US (state MTLs, federal) | EU (MiCA-aligned via licensed CASP partners) | Chains | Base (native) | Base, Polygon, Arbitrum, Optimism, Ethereum, Solana | x402 support | Native (reference) | Native | MPP support | No | Native, on every endpoint alongside x402 | KYA trust scoring | No | Yes, 0-100, ERC-8004 | Sanctions screening on agent wallet | No | Yes, OFAC + EU + UN lists | Self-serve KYB | Coinbase exchange flow | Sumsub, <30 min | Pricing | Coinbase facilitator fee + on-chain gas | 50 bps + partner spread (typically 80-130 bps all-in) | Token / governance | None at facilitator level | None ## When Coinbase CDP is the right call - You are a US-based developer or your treasury is USD-denominated - You are happy receiving USDC and managing the off-ramp yourself (or via Coinbase's exchange) - You only need Base as the on-chain ingress and don't need multi-chain support - You want the reference facilitator with the deepest agent-SDK distribution - You don't need agent-side trust filtering at the facilitator layer (you'll do it elsewhere or accept the residual risk) ## When AsterPay is the right call - You are an EU-incorporated merchant and you want EUR in your bank account, not USDC in a wallet - You want the regulatory perimeter to be EU-resident under MiCA, not US-resident - You want trust-screening on the agent wallet before settlement - You want both x402 and MPP supported on the same response - Your agents may pay from any of Base, Polygon, Arbitrum, Optimism, Ethereum or Solana - You want pricing that is publicly listed without a sales call ## The two are not competitive at the protocol layer x402 is an open protocol. Anyone can run a facilitator. Coinbase CDP's role as the reference facilitator is similar to AWS's role for S3-compatible object storage: canonical, broadly used, and not a barrier to alternative implementations that serve different geographies or feature sets. AsterPay is on the official x402 ecosystem page maintained by Coinbase precisely because the community recognises that EU-native facilitators are needed alongside the canonical CDP one. Plurality is the design intent. ## How they typically coexist in production A US developer building an agent-facing API will start with CDP because it ships out of the box with every x402 SDK. When they get their first European customer who asks for an invoice in EUR with an EU-issued IBAN, they add AsterPay as a second facilitator and route based on customer geography. Alternatively, an EU developer starts with AsterPay (because EUR settlement is a hard requirement from day one) and adds CDP only if they need US-customer flows that prefer USDC custody. Neither path locks the developer into a single vendor; the x402 protocol allows facilitator selection per-request via the response headers. ### Bottom line Coinbase CDP is the canonical x402 facilitator and the right default for US-flavoured stacks. AsterPay is the EU-native facilitator with EUR settlement and KYA trust, and the right default for EU-flavoured stacks. Most production agent-commerce stacks will end up with both. The protocol is designed for that. ### Related comparisons - [All AsterPay comparisons](/compare/) - [How to choose an x402 facilitator in Europe](/learn/best-x402-facilitator-europe/) - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay is not affiliated with Aster (ASTER) DEX, the BNB Chain perpetual exchange, and has no native token. Coinbase Developer Platform is a registered product of Coinbase, Inc. This page is informational and is based on publicly available product documentation as of the date shown. --- # AsterPay vs Dexter β€” x402 facilitators compared | AsterPay Source: Markdown mirror: > Dexter is the highest-volume x402 facilitator (Solana-native). AsterPay is the EU facilitator with EUR SEPA Instant settlement, KYA trust scoring and MiCA-aligned compliance. Honest comparison for choosing between them. [← All comparisons](/compare/) # AsterPay vs Dexter β€” honest comparison Updated 15 July 2026 Β· 5 minute read Β· By Petteri, Co-founder Short answer Dexter is the highest-volume x402 facilitator β€” roughly half of tracked x402 transactions, Solana-native, deeply embedded in agent frameworks. If you want raw crypto-native throughput, Dexter has earned the default slot. AsterPay plays a different game: EUR to an EU merchant's bank via SEPA Instant, per-call agent trust screening (KYA), and a MiCA-aligned compliance posture. Dexter has none of that, and doesn't claim to. Pick by workload, not by market share. ## What each one is Dexter is a crypto-native x402 facilitator that rose to the top of the volume charts in 2026, driven by Solana-native settlement (with Base support) and agent-to-agent payment routing. Its distribution advantage is structural: Dexter is preconfigured as the default facilitator in several agent frameworks, so builders use it without ever making a vendor decision. Settlement stays in stablecoins on-chain. AsterPay , operated by AELIRA LTD (Cyprus), is the EU-native x402+MPP facilitator with fiat settlement: USDC/EURC in, EUR to the merchant's IBAN via SEPA Instant in under 10 seconds. Every payment passes KYA trust scoring (0–100, ERC-8004 identity, sanctions screening) before settlement. Facilitation itself is free forever; AsterPay charges 0.5% + €0.10 when euros reach the bank. ## Side-by-side comparison | | Capability | Dexter | AsterPay | x402 transaction volume | #1 tracked facilitator (~50%) | Small in comparison | Primary chains | Solana (native), Base | Base (primary), Ethereum, Polygon, Arbitrum, Optimism | Settlement currency out | Stablecoins, stays on-chain | EUR via SEPA Instant (<10 s) | Agent trust screening (KYA) | No | Per-call, 0–100, ERC-8004 + sanctions | MPP support | No | Native alongside x402 | EU compliance posture | None claimed | MiCA-aligned via licensed partners, KYB, Travel Rule | Agent-to-agent routing | Yes, a core feature | Via MPE merchant discovery | Framework distribution | Default in several agent frameworks | MCP server, SDKs, directories | Facilitation fee | ~0.1–0.5% | $0 forever | Fiat settlement fee | n/a (no fiat) | 0.5% + €0.10 (EU rail) ## Where Dexter wins - You are Solana-native β€” Dexter is the obvious facilitator there - You want the highest-throughput, battle-tested facilitator for crypto-in, crypto-out flows - Your framework already ships with Dexter configured and you have no fiat or compliance requirement - Agent-to-agent payment routing is central to your product ## Where AsterPay wins - You are an EU merchant who needs euros in a bank account , not stablecoins in a wallet - Your finance or legal team requires KYB, sanctions screening and a MiCA-aligned settlement path - You want the paying agent vetted per call (KYA trust score) before money moves - You need both x402 and MPP accepted on the same endpoint - You want facilitation free, with fees only on fiat settlement ## The honest lesson we take from Dexter Dexter didn't win by out-marketing anyone β€” it won by being preinstalled . When an agent framework ships with a default facilitator, most builders never revisit the choice. We consider that the single most important distribution lesson in the x402 ecosystem, and it is why AsterPay publishes an MCP server, framework templates and machine-readable manifests rather than relying on merchants finding a landing page. On pure crypto-native volume, Dexter deserves its lead. The EUR-settlement and compliance workload is a different race, and it is the one we run. ### Bottom line Crypto-in, crypto-out at maximum volume, especially on Solana β†’ Dexter. USDC in, EUR in an EU bank account with trust screening and compliance β†’ AsterPay. The two barely overlap today; sophisticated stacks route per request. ### Related comparisons - [All AsterPay comparisons](/compare/) - [AsterPay vs Coinbase CDP](/compare/asterpay-vs-coinbase-cdp/) - [AsterPay vs Stripe (x402 + MPP)](/compare/asterpay-vs-stripe-x402-mpp/) - [x402 facilitator fees compared](/learn/x402-facilitator-fees-compared/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay has no native token. Volume figures reference publicly tracked x402 facilitator data (Signal402) as of July 2026 and change over time. This page is informational and based on publicly available documentation as of the date shown. --- # AsterPay vs Skyfire β€” two meanings of "Know Your Agent" (KYA) | AsterPay Source: Markdown mirror: > Skyfire and AsterPay both use the term KYA (Know Your Agent) but mean different things: Skyfire issues agent identity credentials for US enterprise checkout; AsterPay scores agent wallets on-chain (0-100, ERC-8004, sanctions) before EUR settlement in the EU. [← All comparisons](/compare/) # AsterPay vs Skyfire β€” two meanings of "Know Your Agent" Updated 15 July 2026 Β· 6 minute read Β· By Petteri, Co-founder Short answer Both companies use the acronym KYA , and they mean different things. Skyfire's KYA is an issued credential : an agent registers with Skyfire, receives a verifiable identity, and merchants accept it β€” distributed through US enterprise channels. AsterPay's KYA is an on-chain trust score : any agent wallet, registered or not, is scored 0–100 from observable evidence (wallet history, ERC-8004 identity, sanctions lists, operator KYB) at payment time, before EUR settlement. Credentials tell you who vouched for the agent; scoring tells you what the chain says about it right now. The layers are compatible, not interchangeable. ## What each one is Skyfire (US, $9.5M seed) builds an identity and payment layer for AI agents: agents register to receive KYA identity credentials, carry spending wallets, and check out at merchant endpoints, including card-style flows. Skyfire's distribution strategy runs through enterprise infrastructure vendors (its F5 partnership being the flagship example), putting it in front of large US enterprises without direct sales to each one. AsterPay , operated by AELIRA LTD (Cyprus), runs the production KYA trust scorer for the x402 ecosystem: a free, no-auth endpoint that scores any agent wallet 0–100 using wallet age and activity, ERC-8004 on-chain identity, Chainalysis sanctions screening, operator KYB and behavioural history. The score gates AsterPay's own EUR settlement rail (SEPA Instant, 0.5% + €0.10) and is published to the Intuition knowledge graph, so the assessment is portable and publicly verifiable rather than locked inside one vendor's API. ## Side-by-side comparison | | Capability | Skyfire | AsterPay | KYA model | Issued identity credential (register first) | Evidence-based score (works on any wallet) | Coverage of unregistered agents | Not covered | Scored from on-chain evidence | Identity standard | Proprietary credential | ERC-8004 (open standard) + published to Intuition graph | Sanctions screening per payment | At registration/account level | Per call, Chainalysis | Payment rails | Skyfire wallet, card-style checkout | x402 + MPP, stablecoins on Base et al. | Fiat settlement | USD-centric | EUR via SEPA Instant (<10 s) | Regulatory focus | US | EU (MiCA-aligned via licensed partners) | Distribution | Enterprise channel partners (F5) | Agent directories, MCP, SDKs, partner program | Trust score API pricing | Enterprise contract | Free, no auth | Funding | $9.5M seed | Bootstrapped ## Where Skyfire wins - You are a US enterprise whose infra vendor (e.g. F5) already ships Skyfire integration - You want agents to carry an issued, revocable corporate credential rather than be judged on wallet history - You need card-style checkout flows for agents inside a US regulatory perimeter - Vendor financial backing matters to your procurement process ## Where AsterPay wins - You need to assess any agent that shows up β€” most x402 traffic comes from wallets that never registered anywhere - You want the assessment anchored to open standards (ERC-8004) and publicly verifiable on-chain (Intuition graph), not a proprietary credential - You are an EU merchant and the trust check must gate an actual EUR settlement , not just an identity handshake - You want per-call sanctions screening in the payment path - You want to try it now, free, without a sales call: `GET /v1/agent/trust-score/{address}` ## Why the two KYAs are compatible Identity credentials and trust scoring solve different halves of the same problem. A credential says: a known issuer vouches for this agent's operator . A score says: the observable record of this wallet, right now, supports this level of exposure . A mature agent-commerce stack will want both β€” exactly as human finance uses both passports (credentials) and credit scores (behavioural evidence). An agent carrying a Skyfire credential can still be scored by AsterPay before an EU merchant accepts its money. Nothing about the two products is mutually exclusive; only the geographies and rails differ today. ### Bottom line Skyfire owns issued agent credentials in the US enterprise channel. AsterPay owns evidence-based agent scoring on open standards in the EU settlement path. If your question is "can I trust this wallet enough to take its money as euros" β€” that is AsterPay's KYA, and the score endpoint is free. ### Related comparisons - [All AsterPay comparisons](/compare/) - [What is KYA (Know Your Agent)?](/learn/what-is-kya/) - [KYA compliance in the EU](/learn/know-your-agent-compliance-eu/) - [ERC-8004 explained](/learn/erc-8004-explained/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay has no native token. Skyfire is a product of Skyfire Systems, Inc. This page is informational and based on publicly available documentation as of the date shown. --- # AsterPay vs Stripe (x402 + MPP) β€” agent payments in Europe | AsterPay Source: Markdown mirror: > AsterPay vs Stripe for AI agent payments: Stripe [← All comparisons](/compare/) # AsterPay vs Stripe (x402 + MPP) β€” honest comparison Updated 15 July 2026 Β· 6 minute read Β· By Petteri, Co-founder Short answer Stripe is the world's best checkout for human buyers and co-authored MPP, the Machine Payments Protocol. But its x402/MPP agent-payment support is in US-only private preview as of July 2026. AsterPay is live in the EU today: x402 and MPP accepted on every endpoint, EUR settled to your IBAN via SEPA Instant in under 10 seconds, at 0.5% + €0.10 on the EU rail. If your buyers are humans, use Stripe. If your buyers are AI agents and you are an EU merchant, Stripe cannot serve you yet β€” AsterPay can. ## What each one is Stripe is the leading payments platform for internet businesses: cards, wallets, subscriptions, invoicing, fraud tooling and a banking-as-a-service stack. In 2026 Stripe co-published the Machine Payments Protocol (MPP, with Tempo) and began piloting x402 facilitation β€” both currently in private preview for US businesses, settling into the Stripe balance. AsterPay , operated by AELIRA LTD (Cyprus), is an EU-native agent-payments facilitator. It accepts both x402 and MPP on every paid endpoint, screens the paying agent (KYA trust score, sanctions), and settles EUR to the merchant's bank via SEPA Instant. Facilitation (verify + on-chain settle) is free forever; AsterPay charges only when euros reach the merchant's bank. ## Side-by-side comparison | | Capability | Stripe | AsterPay | Agent payments availability (EU) | Not yet β€” US private preview | Live today | x402 support | Private preview (US) | Native, production | MPP support | Co-author (preview) | Native, on every endpoint | Human card checkout | Best in class | Not offered | Settlement currency | Stripe balance β†’ local payout | EUR via SEPA Instant (<10 s) | Agent trust screening (KYA) | Account-level KYC only | Per-call, 0–100, ERC-8004 + sanctions | Micropayments (<$0.10/call) | Card economics don't fit | From $0.001 per call | Facilitation fee | Not public (preview) | $0 forever | EUR settlement fee | ~1.4–2.9% + fixed (card reference) | 0.5% + €0.10 (EU rail) | Regulatory home | US / Ireland (e-money) | EU (MiCA-aligned via licensed partners) | Brand & distribution | Unmatched | Growing, agent-directory listed ## Where Stripe wins - Your buyers are humans : cards, Apple Pay, hosted checkout, subscriptions, invoicing β€” nothing else comes close - You are a US business already inside the MPP/x402 preview and want everything in one Stripe balance - You need Stripe's fraud tooling (Radar) for human-session risk - Brand trust matters to your procurement team more than time-to-live ## Where AsterPay wins - You are an EU merchant and need agent payments today , not when a preview reaches Europe - You want EUR in your bank , not a platform balance β€” SEPA Instant, under 10 seconds - You sell APIs, data or content priced per call, down to $0.001 β€” below card economics - You want the paying agent screened before settlement (KYA + sanctions), not just your own account KYC'd - You want both x402 and MPP on the same endpoint, so any agent can pay regardless of which protocol its framework picked - You want facilitation free and pricing public, without a sales call ## The realistic reading Stripe entering agent payments validates the category β€” MPP exists because Stripe believes machine buyers are real. When Stripe's preview reaches Europe (our estimate: 6–12 months), "USDC in, fiat out" becomes a checkbox inside Stripe. What Stripe will still not have is per-call agent trust screening, EUR-first SEPA Instant settlement as the default rail, and an EU-resident regulatory perimeter. That is the layer AsterPay is building its moat on. Until the preview ships in the EU, the comparison is simpler: one of these products is available to you, the other is not. ### Bottom line Human buyers β†’ Stripe, no contest. AI-agent buyers paying an EU merchant β†’ AsterPay is live today with EUR settlement at 0.5% + €0.10, while Stripe's agent rails remain a US-only preview. Many stacks will eventually run both: Stripe for the human checkout, AsterPay for the agent traffic. ### Related comparisons - [All AsterPay comparisons](/compare/) - [AsterPay vs Coinbase CDP](/compare/asterpay-vs-coinbase-cdp/) - [x402 vs MPP β€” protocol comparison](/learn/x402-vs-mpp/) - [x402 facilitator fees compared](/learn/x402-facilitator-fees-compared/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay has no native token. Stripe and the Machine Payments Protocol are products of Stripe, Inc. This page is informational, based on publicly available documentation as of the date shown; preview-program details may change. --- # How AsterPay compares β€” Stripe, Wise, BVNK, raw x402 | AsterPay Source: Markdown mirror: > Honest, side-by-side comparison of AsterPay vs Stripe, Wise, BVNK and raw x402. We [← Back to AsterPay](/) # Same EUR rail. Built for agents instead of forms. An honest, side-by-side comparison. We're not trying to replace Stripe for your SaaS checkout. We're the rail for when your customers become AI agents β€” and we'll tell you when you should use someone else. ## Side-by-side | | | Stripe | Wise | BVNK | Raw x402 | AsterPay | Best for | Human checkouts | Cross-border FX | Stablecoin B2B | Crypto-native builds | Agent β†’ merchant EUR | Agent-native protocol | MPP only 1 | Γ— | Γ— | x402 only | x402 + MPP 2 | Per-call micropayments | per-txn min | Γ— | Γ— | βœ“ | βœ“ from $0.01 | Agent identity (KYA) | account KYC | account KYC | account KYC | Γ— DIY | ERC-8004 + Trust Score | Sanctions screening per call | at account level | at account level | at account level | Γ— | βœ“ <100 ms / call | EUR settlement speed | 2–7 days | seconds–hours | 1–2 days | crypto only | <10 s SEPA Instant | Merchant discovery by name (MPE) | Γ— | Γ— | Γ— | Γ— | βœ“ MPE + payee validation | EU regulatory base | Ireland | EMI (multi) | UK / MiCA | N/A | Cyprus Β· technical service provider | Time to first payment | 2–5 days | 1–2 days | days | minutes | 60 seconds | EU-rail price (per settled txn) | ~1.4% + €0.25 | 0.43% + fixed | ~0.5–1% | n/a (no EUR) | 0.5% + €0.10 | US-rail price (per settled txn) | ~2.9% + $0.30 | ~0.6% + $4 | varies | n/a | 1.5% + €1.00 1 Stripe MPP launched March 2026; identity and screening remain at the merchant-account level, not per-call. 2 AsterPay verifies the agent on every call (per-call KYA) and screens for sanctions in <100 ms. Competitor pricing is from public pricing pages as of April 2026 and may differ for negotiated accounts. ## EU rail vs US rail β€” which one applies to you? AsterPay runs two settlement rails. We assign you one based on your country of incorporation at KYB onboarding, and we tell you in writing before you go live. We never silently move a merchant between rails. | | | EU rail (default) | US rail | For | EU-incorporated merchants | US-incorporated entities (Delaware C-corp, LLC, …) | Settlement | Direct via licensed European payment partner | Routed via US-licensed banking partner | Per-txn fee | 0.5% + €0.10 | 1.5% + €1.00 | EUR delivered | EUR to your IBAN, <10s SEPA Instant | EUR to your IBAN, typically within minutes | FX handling | USDC / EURC / EURCV β†’ EUR, no markup | USDC β†’ EUR conversion + SEPA passthrough | KYB time | ~10 min | ~30 min (US incorporation docs) | Volume discount | From €50k / month | Available, talk to us ### Why two rails? SEPA is an EU-only network. To settle EUR into a non-EU entity's account legally and reliably, we route through a US-licensed banking partner that handles the cross-border bridge. That partner has higher per-transaction infrastructure costs β€” and we don't hide that. The US rail price reflects the real cost; the EU rail price reflects the (much cheaper) direct route. The technology, dashboard, KYA, screening and audit trail are identical on both rails. Only the underlying banking layer differs. ## When to use AsterPay ### βœ“ Your customers are AI agents (not humans filling forms) If a Claude / ChatGPT / Cursor / OpenAI Operator / your-own-agent is the entity initiating payment, you need per-call KYA, ERC-8004 identity, and HTTP-402 / MPP at the protocol layer. Stripe, Wise and BVNK don't do this β€” they were built when the buyer was a human with a session. ### βœ“ You want EUR (not USD or USDC) in your bank EUR-native settlement to a SEPA Instant IBAN, no FX games, no spread arbitrage on the back end. Crypto-native players settle in USDC and leave you to convert. We don't. ### βœ“ You sell APIs, data, content, or workflows agents can buy Pricing models built for the per-call world β€” from $0.01 micropayments up to enterprise volume. No subscription gating, no minimum monthly. ### βœ“ You need EU compliance posture from day one MiCA-aligned, EU AI Act Article 50 transparency built in, Travel Rule at >€1,000, sanctions screening on every transaction. Cyprus entity, audit-ready. ## When NOT to use AsterPay ### Γ— Your customers are humans clicking "Buy now" Use Stripe . Stripe Checkout, Stripe Elements, Apple Pay, fraud tooling for human sessions β€” we don't do any of that. We're a different layer. ### Γ— You're moving money between business bank accounts Use Wise or your bank's SEPA. We're a payments-acceptance layer, not a treasury / FX tool. ### Γ— You want stablecoins to stay stablecoins Use BVNK or Circle. We exist to convert stablecoins to EUR. If your accounting wants USDC on your balance sheet, you don't need us. ### Γ— You want to roll your own facilitator and self-host everything Use raw x402 β€” the spec is open, the reference impl is on GitHub. You'll handle KYA, sanctions, EUR settlement, banking partners, MiCA-aligned partner routing, Travel Rule and Article 50 yourself. Some teams want that. We exist for the teams that don't. ## The honest summary AsterPay is a narrow product. We're the EU-native EUR settlement layer for AI agent commerce . We win when the buyer is non-human, the seller wants EUR in their bank, and compliance can't be a roadmap item. Outside that, you have better options β€” and we'll point you at them. ## Head-to-head deep dives Each of these pages is a focused side-by-side against one named alternative. - [AsterPay vs Coinbase CDP](/compare/asterpay-vs-coinbase-cdp/) β€” canonical x402 facilitator vs EU-native facilitator with EUR settlement and KYA - [AsterPay vs Stripe (x402 + MPP)](/compare/asterpay-vs-stripe-x402-mpp/) β€” US private preview vs live-in-EU today, card economics vs micropayments - [AsterPay vs Dexter](/compare/asterpay-vs-dexter/) β€” the volume leader (Solana-native, crypto-out) vs the EUR settlement and compliance rail - [AsterPay vs Skyfire](/compare/asterpay-vs-skyfire-kya/) β€” two meanings of "Know Your Agent": issued credentials vs on-chain trust scoring - [x402 facilitator fees compared](/learn/x402-facilitator-fees-compared/) β€” who charges what in 2026, and why facilitation itself is free [Start KYB β†’](/) [Read the docs](/docs/) [Talk to the founder](mailto:petteri@asterpay.io) --- # Contact β€” AsterPay Source: Markdown mirror: > Contact AsterPay β€” EUR settlement layer for AI agent payments. Email, booking link and company details. Operated by AELIRA LTD (Cyprus). [← asterpay.io](/) # Contact EUR settlement layer for AI agent payments. Humans and agents welcome β€” every address below is plain text on purpose. ## Sales & partnerships [samantha@asterpay.io](mailto:samantha@asterpay.io) Or book a call: [cal.eu/asterpay](https://www.cal.eu/asterpay) ## Technical & integrations [petteri@asterpay.io](mailto:petteri@asterpay.io) Docs: [asterpay.io/docs](/docs/) Β· API: [x402.asterpay.io/docs](https://x402.asterpay.io/docs) ## Security & compliance [petteri@asterpay.io](mailto:petteri@asterpay.io) Β· [security.txt](/.well-known/security.txt) ## Social [@Asterpayment](https://x.com/Asterpayment) on X Β· [GitHub](https://github.com/aelira-labs) AELIRA LTD (HE 490977) Β· VAT CY60362013K Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus --- # How to Integrate EUR Settlement in Your x402 Agent | AsterPay Source: Markdown mirror: > Step-by-step guide for AI agent builders: add EUR settlement to your x402 agent. Python SDK, TypeScript, raw HTTP examples. USDC β†’ EUR via SEPA Instant. [← Back to Documentation](/docs/) # How to Integrate EUR Settlement in Your x402 Agent Your AI agent earns USDC via x402. Convert it to EUR and send to any EU bank account via SEPA Instant β€” in under 30 seconds. No signup required. ### TL;DR Call `api.asterpay.io` endpoints β†’ pay USDC on Base via x402 β†’ AsterPay handles EUR conversion & SEPA settlement. Works with Python SDK, TypeScript, or raw HTTP. `pip install asterpay` or `npm install x402-axios` ### Contents - [The Problem](#problem) - [How It Works](#how-it-works) - [Quick Start (3 Options)](#quick-start) - [Available Endpoints](#endpoints) - [Step-by-Step Payment Flow](#step-by-step) - [EUR Settlement for Your Own API](#your-own-api) - [How Agents Discover Your API](#discovery) - [Built-in Compliance](#compliance) - [FAQ](#faq) ## The Problem Your x402 agent gets paid in USDC on Base. That's great for on-chain operations, but useless when you need to: - Pay for a European VPS or cloud service (EUR) - Settle with a European business partner - Cover real-world expenses denominated in EUR - Comply with MiCA regulations for EU operations There's no native EUR settlement in x402 today. AsterPay adds this missing layer. ## How It Works Your Agent earns USDC via x402 ↓ AsterPay receives USDC on Base ↓ Converts to EUR (licensed VASP) ↓ SEPA Instant to any EU/EEA IBAN ↓ EUR in bank account (< 30 seconds) The buyer experience stays identical β€” they pay USDC on Base. The difference is on the settlement side: instead of holding USDC, the service provider receives EUR. ## Quick Start Choose your preferred integration method: ### A Python SDK ``` # Install pip install asterpay # Use from asterpay import AsterPay client = AsterPay() # Free: check what's available health = client.utility.health() catalog = client.discovery.catalog() # Paid: get market data (0.005 USDC) price = client.market.price("bitcoin") # {"symbol": "bitcoin", "price_usd": 98450.23, ...} ``` ### B Coinbase x402 SDK (TypeScript) ``` import { paymentMiddleware } from "x402-axios"; import axios from "axios"; const client = axios.create(); paymentMiddleware(client, "your-wallet-private-key"); // Middleware handles 402 β†’ payment β†’ retry automatically const { data } = await client.get( "https://api.asterpay.io/v1/market/price/bitcoin" ); console.log(data); // { symbol: "bitcoin", price_usd: 98450.23, ... } ``` ### C Raw HTTP (Any Language) ``` # 1. Health check (free) curl https://api.asterpay.io/health # 2. Discovery catalog (free) β€” see all endpoints + pricing curl https://api.asterpay.io/discovery/bazaar # 3. Try a paid endpoint β€” get 402 back with payment details curl -v https://api.asterpay.io/v1/market/price/bitcoin # Response: HTTP 402 Payment Required # Body: PaymentRequirements with amount, payTo, asset, network ``` ## Available Endpoints ### Free Endpoints | Endpoint | Description | `GET /health` | Service status & uptime | `GET /discovery/bazaar` | Machine-readable API catalog | `GET /discovery/endpoints` | Endpoint list with pricing | `POST /v1/util/qr-code` | QR code generation ### Paid Endpoints (USDC on Base) | Endpoint | Price | Description | `GET /v1/market/price/:symbol` | $0.005 | Real-time crypto price | `GET /v1/market/ohlcv/:symbol` | $0.01 | OHLCV candlestick data | `GET /v1/market/trending` | $0.005 | Trending tokens | `POST /v1/ai/summarize` | $0.004 | AI text summarization | `POST /v1/ai/sentiment` | $0.004 | Sentiment analysis | `POST /v1/ai/translate` | $0.02 | Multi-language translation | `POST /v1/ai/code-review` | $0.05 | Code review & suggestions | `GET /v1/crypto/wallet-score/:address` | $0.05 | Wallet reputation score | `GET /v1/crypto/token-analysis/:address` | $0.10 | Token security analysis | `GET /v1/crypto/whale-alerts` | $0.02 | Whale movement alerts | `POST /v1/util/screenshot` | $0.02 | Webpage screenshot | `POST /v1/util/pdf-generate` | $0.03 | HTML to PDF conversion ## Step-by-Step: x402 Payment Flow ### 1 Call the Endpoint ``` curl -v https://api.asterpay.io/v1/market/price/bitcoin ``` Response: `HTTP/1.1 402 Payment Required` ### 2 Parse PaymentRequirements ``` { "x402Version": 2, "scheme": "exact", "network": "base", "maxAmountRequired": "5000", "amount": "5000", "resource": "https://api.asterpay.io/v1/market/price/bitcoin", "payTo": "0xF9035b2643EFa7266805219719971fFC7aC88170", "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "extra": { "name": "AsterPay", "description": "Real-time crypto price" } } ``` Key fields: `payTo` = AsterPay wallet on Base. `asset` = USDC contract. `amount` = 5000 micro-USDC = $0.005. `network` = base. ### 3 Sign & Pay Create an EIP-3009 `transferWithAuthorization` signature, attach it as the `X-PAYMENT` header, and retry: ``` import { ethers } from "ethers"; const wallet = new ethers.Wallet(PRIVATE_KEY, provider); // Sign EIP-3009 transferWithAuthorization const signature = await signTransferWithAuthorization( wallet, USDC_ADDRESS, payTo, amount, validAfter, validBefore, nonce ); // Retry with payment header const response = await fetch( "https://api.asterpay.io/v1/market/price/bitcoin", { headers: { "X-PAYMENT": JSON.stringify({ x402Version: 2, scheme: "exact", network: "base", payload: { signature, authorization: { from: wallet.address, to: payTo, value: amount, validAfter, validBefore, nonce }} }) } } ); ``` ### 4 Receive Data ``` { "symbol": "bitcoin", "price_usd": 98450.23, "price_eur": 91200.15, "change_24h": 2.45, "market_cap": 1940000000000, "volume_24h": 45000000000 } ``` ## EUR Settlement for Your Own x402 API Want to add EUR settlement to your own x402-enabled API? AsterPay acts as a facilitator. Agent calls your API ↓ Your API returns 402 (via AsterPay facilitator) ↓ Agent pays USDC to AsterPay ↓ AsterPay verifies β†’ forwards request β†’ returns data ↓ AsterPay converts USDC β†’ EUR β†’ SEPA Instant to your IBAN ``` // Your API server β€” AsterPay handles payment + EUR settlement import { x402Middleware } from "@asterpay/x402-facilitator"; app.use(x402Middleware({ payTo: "0xYourWalletAddress", network: "base", facilitator: "https://api.asterpay.io/v1/facilitator", settlementCurrency: "EUR", iban: "DE89370400440532013000", })); // Your paid endpoint app.get("/v1/your-data", (req, res) => { res.json({ data: "your valuable data" }); }); ``` Fee: 1.0% of transaction value. Settlement via SEPA Instant (< 30 seconds). Available 24/7/365 to any EU/EEA IBAN. ## How Agents Discover Your API ### 1. x402 Protocol (Automatic) Any HTTP client that handles 402 responses will automatically discover pricing and payment details. No registration needed. ### 2. API Bazaar (Machine-Readable Catalog) ``` curl https://api.asterpay.io/discovery/bazaar # Returns structured catalog: descriptions, schemas, pricing, examples ``` ### 3. MCP Server (for AI Agents) ``` npx @asterpay/mcp-server # 12 commerce tools for AI agents using Claude, GPT, etc. ``` ### 4. Python SDK ``` endpoints = client.discovery.endpoints() # Full endpoint list with pricing and I/O schemas ``` ## Built-in Compliance Every transaction through AsterPay is screened automatically: - Chainalysis Sanctions Oracle β€” Real-time OFAC/EU/UN sanctions screening - Risk Scoring β€” Wallet age, volume, velocity, ERC-8004 identity - MiCA Travel Rule β€” Automatic tracking for cumulative EUR thresholds (€1,000) - ERC-8004 Identity β€” On-chain AI agent identity (AsterPay = Agent #16850) Your agent doesn't need to handle compliance β€” AsterPay does it at the protocol level. Sanctioned wallets are blocked automatically (fail-closed). ## FAQ ### Do agents need KYC? No. AsterPay operates under its licensed VASP partner. Individual agents don't need separate KYC. Sanctioned wallets are blocked automatically. ### What's the minimum payment? $0.004 USDC (the cheapest endpoint: AI summarization). No minimum for EUR settlement. ### How fast is EUR settlement? SEPA Instant: under 30 seconds to any EU/EEA bank account. Available 24/7/365. ### What if my agent is on Solana or Ethereum? Multi-chain support is coming. Currently, x402 payments are on Base (cheapest gas). Use Circle's CCTP to bridge USDC from other chains to Base. ### Is there a sandbox? Use the free endpoints (`/health`, `/discovery/bazaar`) to test connectivity, then make a $0.004 AI call to verify the full payment flow. ### How do I monitor spending? Every transaction is on-chain (Base). Track via [BaseScan](https://basescan.org) or the AsterPay dashboard. ### Ready to integrate? Start with `pip install asterpay` and make your first call in 60 seconds. [Get the Python SDK](https://pypi.org/project/asterpay/) [Full Documentation](/docs/) ## Resources - API: [api.asterpay.io](https://api.asterpay.io) - Python SDK: [pypi.org/project/asterpay](https://pypi.org/project/asterpay/) - MCP Server: [clawhub.ai/AsterPayDev/asterpay](https://clawhub.ai/AsterPayDev/asterpay) - x402 Protocol: [x402.org](https://x402.org) - x402 Community: [Coinbase Developer Platform Discord](https://discord.gg/cdp) - Twitter: [@Asterpayment](https://twitter.com/Asterpayment) - ERC-8004: Agent #16850 on Base Mainnet AsterPay β€” Every stablecoin. Every chain. One EUR bank transfer. --- # Documentation - AsterPay | The Trust Layer for AI Agent Payments Source: Markdown mirror: > AsterPay API documentation. The trust, discovery and EUR-settlement layer for AI agent commerce. Seven trust signals in a 4-layer framework, Trust Score 0-100, EUR via SEPA Instant. Know Your Agent (KYA), x402, MPP, x402r escrow, MiCA-aligned via licensed partners. [← Back to AsterPay](/) # Documentation The trust, discovery and EUR-settlement layer for AI agent commerce. Seven trust signals in a 4-layer framework, Trust Score 0–100. EUR in seconds. ### What is AsterPay? AsterPay is the trust, discovery and EUR-settlement layer for AI agent commerce . Every payment passes through a 4-layer framework built from seven trust signals: on-chain agent identity (ERC-8004), enterprise sanctions / AML screening, Trust Score computation, and EUR settlement (EUR via SEPA Instant; GBP and USD via partner rails where available). MiCA-aligned via licensed European partners. Dual-protocol facilitator: x402 + MPP (Stripe / Tempo) + Google AP2 compatibility, plus x402r escrow / refunds. 4 layers: Identify β†’ Screen β†’ Settle β†’ Comply ## Quick Start Get started in under 2 minutes. The Trust Score API is free β€” no signup needed. ### 1. Check an agent's trust score (free, no auth) ``` # Check any agent wallet β€” no API key, no payment curl https://x402.asterpay.io/v1/agent/trust-score/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 # Response: # { "trustScore": 34, "tier": "verified", "maxPerTx": 1000, ... } ``` ### 2. (Optional) Create an account for the dashboard You do not need an API key to call the API β€” free endpoints are open and paid endpoints authenticate by payment (see [Authentication](#authentication)). Only create an account at [app.asterpay.io](https://app.asterpay.io/signup) if you want a dashboard sandbox API key for usage tracking and analytics. ### 3. Test with the API Playground Use the built-in [API Playground](https://app.asterpay.io/playground) to make test requests instantly β€” no code required. ### 4. Make your first x402 request ``` # The x402 flow: request β†’ 402 β†’ pay USDC β†’ retry β†’ 200 # Step 1: Request a paid endpoint (returns 402 + payment requirements) curl https://x402.asterpay.io/v1/market/price/bitcoin # Step 2: Use @x402/fetch to handle payment automatically npm install @x402/fetch ``` ### 5. Submit KYB for production EUR settlement When you're ready to receive EUR, submit a [KYB application](https://app.asterpay.io/kyb) from the dashboard. Approval enables stablecoin β†’ EUR settlement to your bank account. ## How x402 Works The x402 payment flow: - Client requests a paid API endpoint - Server responds with `402 Payment Required` + payment details (USDC amount, address) - Client signs a USDC `transferWithAuthorization` on Base - Client retries the request with `PAYMENT-SIGNATURE` header - Server verifies payment, settles on-chain, returns `200` with data - (Optional) AsterPay converts USDC β†’ EUR via SEPA Instant to your bank ### x402r: Escrow & Refund Protection Trust-to-Refund Pipeline: AsterPay's x402r integration adds on-chain escrow and automated refunds to x402 payments. The agent's KYA Trust Score determines the payment scheme: - Score β‰₯ 70 β†’ `exact` scheme β€” direct payment, instant settlement, no escrow - Score < 70 or unknown β†’ `commerce` scheme β€” funds held in on-chain escrow - AsterPay's KYA Arbiter automatically verifies API delivery (HTTP status, response body, error detection) - If delivery fails β†’ automatic on-chain refund. If delivery verified β†’ escrow releases to provider Protocol: [x402r.org](https://x402r.org) β€” SDK: `@x402r/sdk` ## API Reference ### Know Your Agent (KYA) β€” FREE GET `/v1/agent/trust-score/:address` FREE Full agent trust assessment. Returns Trust Score (0-100), tier, breakdown of 7 components, ERC-8004 identity check, sanctions screening, and wallet analysis. GET `/v1/agent/verify/:address` FREE Quick ERC-8004 identity check. Returns whether the agent is registered in the on-chain identity registry on Base. GET `/v1/agent/tier/:address` FREE Fast tier lookup. Returns agent tier (open/verified/trusted/enterprise) and transaction limits. POST `/v1/agent/trust-score/batch` FREE Batch trust assessment for up to 50 agent addresses at once. GET `/v1/agent/framework` FREE Returns the full KYA framework documentation: layers, tiers, score components, and premium endpoints. GET `/v1/agent/audit/:address` FREE KYA audit snapshot. Returns raw inputs and score breakdown for third-party verification and compliance auditing. GET `/v1/agent/discovery` FREE Service discovery endpoint. Lists all available endpoints, payment methods (x402, MPP), and settlement capabilities. ### Agent Deep Analysis β€” PREMIUM (x402) GET `/v1/agent/deep-analysis/:address` $0.01 Behavioral intelligence: velocity scoring, consistency analysis, funding source risk, and actionable recommendations (allow/limit/review/block). POST `/v1/agent/deep-analysis/batch` $0.05 Batch deep analysis for up to 10 agents. Includes all behavioral signals and recommendations. ### Market Data β€” FREE (freemium) Commodity market data is free as a funnel β€” no payment, no auth. Paid v2 variants with x402 402-quotes exist for agents that want machine-payable equivalents: `GET /v2/x402/crypto/prices` ($0.005), `POST /v2/x402/ai/sentiment` ($0.01). GET `/v1/market/price/:symbol` FREE Get current price, 24h change, market cap, and volume for any crypto asset. GET `/v1/market/ohlcv/:symbol` FREE OHLCV candle data (1–90 days). Symbols: BTC, ETH, SOL, USDC, and 20+ more. GET `/v1/market/trending` FREE Trending coins with price, rank, and 24h change. ### AI Tools POST `/v1/ai/summarize` FREE AI-powered text summarization. POST `/v1/ai/sentiment` FREE Sentiment analysis on any text. Paid v2 variant: `POST /v2/x402/ai/sentiment` ($0.01). POST `/v1/ai/translate` FREE AI translation between languages. POST `/v1/ai/code-review` $0.05 Automated code review with suggestions. ### Crypto Analytics GET `/v1/crypto/wallet-score/:address` $0.05 On-chain wallet reputation score. GET `/v1/crypto/token-analysis/:address` $0.10 Deep token analysis with holder data and risk assessment. GET `/v1/crypto/whale-alerts` FREE Real-time large transaction alerts. ### Utilities POST `/v1/util/qr-code` FREE Generate QR codes from any data. Free gateway endpoint. POST `/v1/util/screenshot` $0.02 Capture a screenshot of any URL. POST `/v1/util/pdf-generate` $0.03 Generate PDF documents from HTML/data. ### Settlement GET `/v1/settlement/estimate` FREE Get a real-time USDC β†’ EUR conversion estimate. GET `/v1/settlement/quote` FREE Get a settlement quote with fees and delivery time. ### Facilitator (x402 v2) POST `/v2/x402/verify` Verify an x402 payment payload. POST `/v2/x402/settle` Settle an x402 payment on-chain. GET `/v2/x402/supported` FREE List supported payment schemes and networks. ### x402r β€” Escrow & Refunds GET `/v1/x402r/status` FREE x402r operator configuration, escrow parameters, and Trust-to-Scheme routing rules. Shows whether escrow-protected payments are active. GET `/v1/x402r/scheme/:address` FREE Determine which payment scheme an agent qualifies for based on KYA trust score. Score β‰₯ 70 β†’ direct payment (exact). Score < 70 β†’ escrow-protected (commerce, refundable). POST `/v1/x402r/arbiter/verify` FREE Automated delivery verification endpoint. Called after settlement to verify API response validity. KYA engine acts as arbiter β€” no human needed. GET `/v1/x402r/refunds/:hash` FREE Check refund status by payment hash. Returns escrow state, approved amount, and dispute resolution status. GET `/v1/x402r/info` FREE x402r protocol information and integration guide. SDK links, arbiter details, and trust-to-scheme documentation. ### Discovery & System GET `/discovery/resources` FREE x402 Bazaar resource discovery (ERC-8004 compatible). GET `/health` FREE Health check. GET `/docs` FREE Interactive Swagger API documentation. ## Authentication One rule per surface β€” you almost never need an API key. | Surface | Auth | How | Free read endpoints | None | Plain HTTP GET. No key, no account. | Paid endpoints | Pay-per-call (keyless) | x402 `PAYMENT-SIGNATURE` header, or MPP `Authorization: Payment`. No account. | Dashboard & merchant features | API key | `Authorization: Bearer sk_...` β€” optional, only for dashboard-bound calls. Live EUR payout requires KYB (handled once, at settlement β€” not at the API). Reads and per-call payments stay keyless and accountless. ### x402 Payment (primary) All paid endpoints use the x402 protocol. No API key needed β€” payment is the authentication. Your client signs a USDC transaction and includes it in the request header. ### API Keys (optional, for tracking) Create API keys in the [dashboard](https://app.asterpay.io/api-keys) to track usage, set rate limits, and view analytics. ``` curl -H "Authorization: Bearer sk_sand_your_key" \ https://x402.asterpay.io/v1/market/price/bitcoin ``` | Key Prefix | Environment | Description | `sk_sand_` | Sandbox | Testing, no real payments | `sk_live_` | Production | Real USDC payments + EUR settlement ## Errors Every error returns the same JSON shape. The HTTP status tells you what to do; the body never leaks internal detail. ``` { "error": "payment_identifier_conflict", "message": "Human-readable explanation.", "x402Version": 2 } ``` | Status | Error | Meaning & what to do | `400` | `bad_request` / `payment_identifier_required` | Malformed request or a required field is missing. Fix the request β€” do not retry as-is. | `402` | `Payment Required` | Paid endpoint hit without a valid payment. The body carries the x402 payment requirements (`accepts`, amount, network, asset). Sign and retry. A failed proof returns `402` with `Payment verification failed`. | `404` | `not_found` | Unknown route or resource (e.g. an address with no data). Do not retry. | `409` | `payment_identifier_conflict` | You reused a `payment-identifier` `id` with a different payment payload. Use a fresh `id` for a new charge (see Idempotency). | `422` | `validation_error` | Request was well-formed but failed validation (bad amount, unsupported chain/asset, out-of-range parameter). Correct the input. | `429` | `rate_limited` | Too many requests. Honour the `Retry-After` and `X-RateLimit-*` response headers and back off. | `403` | `kya_blocked` | Know-Your-Agent gate denied the payer (sanctioned address or trust score below the endpoint's floor). Not retryable for that wallet. | `503` | `settlement_unavailable` | A downstream rail (SEPA / settlement partner) is temporarily unavailable, or an escrow timed out. The charge is not finalised; retry later or re-quote. | `500` | `internal_error` | Unexpected server error. Safe to retry with the same idempotency `id`; if it persists, contact support with the `X-Request-Id`. ## Idempotency Paid calls are safe to retry without double-charging . AsterPay implements the x402 [payment-identifier](https://docs.x402.org/extensions/payment-identifier) extension, advertised in the `extensions` object of every paid `402` response. Attach a unique `id` (16–128 chars) inside the payment payload. Then: - Same `id` + same signed payload β†’ the original `2xx` result is replayed from cache without re-settling on-chain . The replay carries an `X-Idempotency-Replayed: true` header. - Same `id` + different payload β†’ `409 payment_identifier_conflict`. Use a fresh `id` for each distinct charge. - No `id` β†’ normal flow. The underlying USDC authorization carries a one-time EIP-3009 nonce, so a fully identical replay still cannot settle twice on-chain β€” but for guaranteed exactly-once application results, always send an `id`. Generate one `id` per logical operation (e.g. a UUID) and reuse it across network retries of that same operation. ## Supported Chains | Chain | Stablecoins | Status | Base | USDC, EURC | βœ… Primary | Base Sepolia | USDC | βœ… Testnet | Ethereum | USDC, EURC, EURCV | βœ… Supported | Polygon | USDC | βœ… Supported | Arbitrum | USDC | βœ… Supported | Optimism | USDC | βœ… Supported | Bitcoin Lightning | β€” (sats, sub-cent micropayments) | βœ… Supported | Solana | USDC | 🚧 Roadmap | XRPL | XRP, RLUSD | 🚧 Roadmap | Monad | USDC | 🚧 Roadmap ## EUR Settlement AsterPay converts your stablecoin earnings to EUR and sends them to your bank account. - EUR: SEPA Instant β€” in your bank in seconds - GBP: Faster Payments β€” on the roadmap - USD: ACH β€” on the roadmap - Stablecoins: USDC, EURC (Circle), EURCV (SG-FORGE / Société Générale) - Requirements: Approved KYB + bank account on file - MiCA: MiCA-aligned β€” settlement routed via licensed European partners (AsterPay operates as a technical service provider) ## Agent Trust Score Every agent that interacts with AsterPay receives a Trust Score (0–100). The score is built from seven signals organised under a 4-layer framework (IDENTIFY / SCREEN / SETTLE / COMPLY). Two optional endpoint-quality signals can additionally contribute when the caller passes `?endpoint={URL}` β€” the authoritative machine-readable spec is [/v1/agent/framework](https://x402.asterpay.io/v1/agent/framework): | Signal | Max Points | Source | Wallet Age | 15 | On-chain (first tx) | Wallet Activity | 15 | Transaction count | Sanctions Screening | 20 | Chainalysis Sanctions Oracle, on-chain (OFAC, EU, UN) | Agent Identity | 20 | ERC-8004 on-chain registry | Operator KYB | 20 | Off-chain KYB & UBO verification | Payment History | 5 | AsterPay track record | Trust Bond | 5 | Cryptographically attested USDC collateral Scores map to access tiers (synchronised with the machine-readable spec at [/v1/agent/framework](https://x402.asterpay.io/v1/agent/framework)): | Tier | Score | Max Per Call | Daily Cap | Live | Open | 0–19 | $1 | $10 | βœ“ | Verified | 20–49 | $1,000 | $5,000 | βœ“ | Trusted | 50–79 | $10,000 | $50,000 | βœ“ | Enterprise | 80–100 | Negotiated | Negotiated | Q3 2026 Trust tier limits are reviewed quarterly. AsterPay reserves the right to escrow, hold or refuse transactions where risk monitoring requires it β€” see [Terms Β§ 4](/terms/). ## SDKs ### @asterpay/x402 (TypeScript/JavaScript) x402 protocol client with AI Agent Wallet and LangChain integration. ``` # Install npm install @asterpay/x402 # Usage import { createX402Client, createAgentWallet } from '@asterpay/x402'; const wallet = createAgentWallet({ privateKey: process.env.AGENT_KEY, network: 'base', spendingLimits: { daily: 10 } }); const client = createX402Client({ wallet }); const response = await client.fetch('https://x402.asterpay.io/v1/market/price/bitcoin'); ``` ### asterpay (Python) Full Python SDK with async support. CrewAI and LangChain integrations included. ``` # Install pip install asterpay # Usage from asterpay import AsterPay client = AsterPay(api_key="sk_live_...") score = client.discovery.trust_score("0xd8dA...96045") print(score.trust_score, score.tier) # 34, "verified" # Async import asyncio from asterpay import AsyncAsterPay async def main(): client = AsyncAsterPay(api_key="sk_live_...") price = await client.market.get_price("bitcoin") print(price) ``` ### asterpay-openai-agents (Python) Payment tools for OpenAI Agents SDK β€” give your AI agents the ability to pay. ``` # Install pip install asterpay-openai-agents # Usage from agents import Agent from asterpay_agents import get_asterpay_tools, AsterPayWallet wallet = AsterPayWallet( private_key=os.environ["AGENT_KEY"], network="base", daily_limit=10.0 ) agent = Agent( name="Shopping Assistant", tools=get_asterpay_tools(wallet) ) ``` ### @asterpay/attest (CLI & SDK β€” EU AI Act) Scan your TypeScript project for AI SDK imports, run compliance signal checks, and generate EU AI Act documentation. August 2, 2026 deadline. ``` # Zero install β€” try now npx @asterpay/attest scan # Check compliance signals npx @asterpay/attest check # Generate Annex IV docs npx @asterpay/attest docs -o ./compliance ``` [GitHub](https://github.com/aelira-labs/attest) Β· [npm](https://www.npmjs.com/package/@asterpay/attest) Β· MIT License ## Agent-to-Agent Payments (Payment Rail Propagation) AsterPay's MCP server includes two tools for the x402 "virus machine" pattern β€” payment rails that propagate automatically between agents: ### agent_pay β€” Pre-payment trust gate Before paying another agent, call `agent_pay` to verify they're not sanctioned and check their trust tier. Returns payment instructions if safe, blocks if sanctioned. ``` # Via MCP: agent checks trust before sending USDC # β†’ Returns: trust score, sanctions status, payment instructions # β†’ Blocks sanctioned addresses automatically # β†’ Recommends escrow for low-trust agents (score Returns AsterPay's payment rail as a JSON-LD document. Install this rail to pay any AsterPay-connected agent, then forward it to every agent you interact with. ``` # Returns JSON-LD payment rail with: { "@context": { "x402": "https://x402.org/schema/" }, "x402:signatureScheme": "ECDSA-SHA256", "x402:supportedNetworks": ["Base", "Ethereum", "Polygon", ...], "asterpay:trustScoring": { "scoreRange": "0-100" }, "asterpay:settlement": { "currencies": ["EUR", "USD", "GBP"] } } ``` Discovery: [.well-known/x402.json](https://asterpay.io/.well-known/x402.json) (JSON-LD) Β· Signature: ECDSA-SHA256 ## Code Examples ### Trust Score β€” cURL (free) ``` # Get full trust assessment for any wallet curl https://x402.asterpay.io/v1/agent/trust-score/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 # Quick tier check curl https://x402.asterpay.io/v1/agent/tier/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 # Batch check 10 agents at once curl -X POST https://x402.asterpay.io/v1/agent/trust-score/batch \ -H "Content-Type: application/json" \ -d '{"addresses": ["0xd8dA...", "0xABC..."]}' ``` ### Trust Score β€” Python ``` from asterpay import AsterPay client = AsterPay() result = client.discovery.trust_score("0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045") if result.tier in ("trusted", "enterprise"): process_payment(result.wallet) elif result.screening.sanctioned: block_wallet(result.wallet) else: require_additional_verification(result.wallet) ``` ### Node.js β€” Fetch with x402 payment ``` import { fetchWithPayment } from '@x402/fetch'; const response = await fetchWithPayment( 'https://x402.asterpay.io/v1/ai/summarize', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ text: 'Your text here...' }) }, wallet ); ``` ### Python β€” Market data ``` import requests # Free endpoint (no payment needed) r = requests.get("https://x402.asterpay.io/v1/settlement/estimate", params={"amount": "100"}) print(r.json()) # { "eur": "92.50", "rate": 0.925, ... } ``` ### cURL β€” Check supported networks ``` curl https://x402.asterpay.io/v2/x402/supported ``` ## Webhooks Configure webhooks in the [dashboard](https://app.asterpay.io/webhooks) to receive real-time notifications. ``` // Webhook payload example { "event": "settlement.completed", "transaction_id": "txn_abc123", "amount_usdc": "100.00", "amount_eur": "92.50", "status": "settled", "sepa_reference": "ASTER-2026-0213" } ``` ## Dashboard The [AsterPay Dashboard](https://app.asterpay.io) gives you full control: - API Keys β€” Create and manage sandbox & production keys - Playground β€” Test all endpoints interactively (including Trust Score) - Usage Analytics β€” Real-time charts for requests, revenue, and latency - Transactions β€” Track stablecoin payments and EUR settlements - Budgets β€” Set daily/weekly/monthly spending limits for AI agents - CRM β€” Lead pipeline and outreach tracking - Webhooks β€” Configure event notifications - Team β€” Invite team members with role-based access - KYB β€” Submit your business verification for production EUR settlement ## Infrastructure Partners - [Drip](https://drippay.dev) β€” Usage metering, anomaly detection, and real-time webhooks. Every API call is tracked via Drip for usage analytics and billing intelligence. - [InsumerAPI](https://insumermodel.com) β€” On-chain attestation provider across 32 chains. Powers the credential and activity layers of our KYA Trust Score. ## Support We're here to help you integrate fast. - Email: [samantha@asterpay.io](mailto:samantha@asterpay.io) - Community: [t.me/asterpaycommunity](https://t.me/asterpaycommunity) - Interactive API docs: [Swagger UI](https://x402.asterpay.io/docs) --- # x402 Tutorial - AsterPay Documentation Source: Markdown mirror: [πŸ“¦ AsterPay Docs](/) [Overview](/docs/) [x402 Tutorial](/docs/x402-tutorial.html) [GitHub](https://github.com/aelira-labs) # How to Implement x402 Payments with AsterPay The Complete Guide to AI Agent Payments + EUR Off-Ramp ⏱️ ~15 min read πŸ’» TypeScript πŸ”— Base, Polygon, Arbitrum, BSC #### πŸ“‹ Table of Contents - [Overview](#overview) - [Part 1: Setting Up the Server (Seller)](#part1) - [Part 2: Creating the AI Agent Client (Buyer)](#part2) - [Part 3: EUR Off-Ramp Integration](#part3) - [Part 4: LangChain Integration](#part4) - [Part 5: Production Deployment](#part5) - [Security Best Practices](#security) ## Overview x402 is the open protocol for internet-native payments, using HTTP 402 "Payment Required" to let AI agents and services pay each other instantly. AsterPay is an x402 Facilitator that adds: - πŸ‡ͺπŸ‡Ί EUR Off-Ramp β€” USDC β†’ EUR via SEPA in <30 minutes - πŸ€– AI Agent Wallets β€” Spending limits and controls - πŸ”— Multi-Chain β€” Base, Polygon, Arbitrum, BSC, Ethereum - ⚑ 1.0% Fees β€” volume-based discounts available In this guide, you'll build: - An x402-protected API endpoint - An AI agent that pays for API calls automatically - EUR off-ramp integration for European developers ### What You Will Need - Node.js v18+ installed - Basic TypeScript/JavaScript knowledge - An EVM wallet with testnet USDC (Base Sepolia) - AsterPay API key (get one at [app.asterpay.io](https://app.asterpay.io)) ## Part 1: Setting Up the Server (Seller) ### Step 1: Initialize Project ``` mkdir asterpay-x402-demo cd asterpay-x402-demo npm init -y npm install express @asterpay-io/x402 dotenv npm install -D typescript @types/express @types/node ts-node ``` ### Step 2: Environment Variables Create `.env`: ``` # Your wallet address (receives payments) WALLET_ADDRESS=0xYourWalletAddressHere # AsterPay API Key (get from dashboard) ASTERPAY_API_KEY=ap_live_xxxxxxxxxxxx # Network (base-sepolia for testing, base for production) NETWORK=base-sepolia # Server port PORT=3000 ``` ### Step 3: Create the x402 Protected Server ``` import express from 'express'; import { createX402Middleware, X402Config } from '@asterpay-io/x402'; import dotenv from 'dotenv'; dotenv.config(); const app = express(); app.use(express.json()); // AsterPay x402 Configuration const x402Config: X402Config = { payTo: process.env.WALLET_ADDRESS!, network: process.env.NETWORK as 'base' | 'base-sepolia', facilitator: { url: 'https://x402.asterpay.io', apiKey: process.env.ASTERPAY_API_KEY }, // Optional: EUR off-ramp eurOfframp: { enabled: true, iban: process.env.EUR_IBAN } }; // Create middleware with pricing const x402Middleware = createX402Middleware(x402Config, { 'GET /api/market-data': { price: '$0.005' }, 'GET /api/ai-analysis': { price: '$0.004' }, 'POST /api/generate-image': { price: '$0.10' }, }); app.use(x402Middleware); // Market data endpoint - $0.005 per request app.get('/api/market-data', (req, res) => { res.json({ symbol: 'BTC', price: 98542.50, timestamp: new Date().toISOString() }); }); const PORT = process.env.PORT || 3000; app.listen(PORT, () => { console.log(`πŸš€ x402 API running on http://localhost:${PORT}`); }); ``` ## Part 2: Creating the AI Agent Client (Buyer) ``` import { AgentWallet, createX402Fetch } from '@asterpay-io/x402'; async function main() { // Create AI Agent Wallet with Spending Limits const agentWallet = new AgentWallet({ privateKey: process.env.AGENT_PRIVATE_KEY!, network: 'base-sepolia', // Spending controls - critical for AI agents! spendingLimits: { perTransaction: 0.10, // Max $0.10 per tx daily: 5.00, // Max $5.00 per day monthly: 50.00 // Max $50.00 per month } }); console.log('πŸ€– Agent Wallet:', agentWallet.address); console.log('πŸ’° Balance:', await agentWallet.getBalance(), 'USDC'); // Create x402-enabled Fetch (auto-handles payments) const x402Fetch = createX402Fetch(agentWallet); // Make Paid API Call const response = await x402Fetch('http://localhost:3000/api/market-data'); const data = await response.json(); console.log('Data:', data); } main(); ``` ## Part 3: EUR Off-Ramp Integration β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”‚ AI Agent │────▢│ AsterPay │────▢│ Settlement │────▢│ Your Bank β”‚ β”‚ Pays USDC β”‚ β”‚ Facilitatorβ”‚ β”‚ SEPA API β”‚ β”‚ (EUR) β”‚ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ $0.10 Verify Convert €0.09 Settle USDC β†’ EUR <30 min ``` const x402Config: X402Config = { payTo: process.env.WALLET_ADDRESS!, network: 'base', facilitator: { url: 'https://x402.asterpay.io', apiKey: process.env.ASTERPAY_API_KEY }, // Enable EUR off-ramp eurOfframp: { enabled: true, iban: 'FI21 1234 5600 0007 85', // Your IBAN autoConvert: true, minAmount: 10.00, schedule: 'daily' } }; ``` ## Part 4: LangChain Integration ``` import { ChatOpenAI } from '@langchain/openai'; import { createOpenAIToolsAgent } from 'langchain/agents'; import { AsterPayTool } from '@asterpay-io/x402/langchain'; // Create AsterPay tool for LangChain const asterPayTool = new AsterPayTool({ wallet: agentWallet, description: 'Pay for external API services using x402' }); // Create agent with payment capability const agent = await createOpenAIToolsAgent({ llm: new ChatOpenAI({ modelName: 'gpt-4' }), tools: [asterPayTool], prompt: agentPrompt }); // Agent can now pay for services automatically const result = await executor.invoke({ input: 'Get the current BTC price from the market API' }); ``` ## Part 5: Production Deployment ### Vercel Deployment ``` { "version": 2, "builds": [ { "src": "src/server.ts", "use": "@vercel/node" } ], "routes": [ { "src": "/(.*)", "dest": "src/server.ts" } ] } ``` ``` vercel env add WALLET_ADDRESS vercel env add ASTERPAY_API_KEY vercel --prod ``` ## Security Best Practices ⚠️ Important: Never use your main wallet for AI agents. Always create dedicated agent wallets with strict spending limits. ``` // βœ… DO: Use dedicated agent wallet with limits const agentWallet = new AgentWallet({ privateKey: AGENT_SPECIFIC_KEY, spendingLimits: { perTransaction: 0.10, daily: 5.00 }, // Only allow payments to trusted APIs allowedRecipients: [ '0xTrustedAPI1...', '0xTrustedAPI2...' ] }); ``` ### Ready to Get Started? Create your free AsterPay account and get your API key in seconds. [Get API Key β†’](https://app.asterpay.io/signup) ## Resources - [AsterPay Documentation](https://asterpay.io/docs) - [x402 Protocol Specification](https://x402.org) - [GitHub Examples](https://github.com/aelira-labs) - [Telegram Community](https://t.me/asterpaycommunity) Β© 2026 AELIRA LTD (HE 490977) | [asterpay.io](https://asterpay.io) | [@Asterpayment](https://twitter.com/Asterpayment) --- # Ecosystem β€” AsterPay Integration Partners Source: Markdown mirror: > AsterPay ecosystem directory: identity, settlement, infrastructure, and agent platform integrations. x402 + MPP dual protocol. EUR settlement via SEPA Instant. [AsterPay](/) [Product](/#product) [Integration](/#sdks) [Dashboard](https://app.asterpay.io) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Create Free Account](https://app.asterpay.io/signup) [Home](/) [Product](/#product) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Create Free Account](https://app.asterpay.io/signup) # The AsterPay ecosystem Protocols, identity providers, analytics platforms, and agent infrastructure with live integrations to AsterPay. Listed partners also appear in our machine-readable discovery files. 6 Partners listed Open Free to apply x402 + MPP Dual protocols EU MiCA Β· AI Act Want your integration listed? The ecosystem partner program is free and open to all qualifying integrations. [Apply to integrate β†’](/partners/) πŸ” ## Identity & attestation I ### InsumerAPI ECOSYSTEM PARTNER On-chain attestations across 32 chains. Powers KYA credential layers for trust scoring and agent identity verification. [insumermodel.com β†’](https://insumermodel.com) πŸ“Š ## Analytics & operations D ### Drip ECOSYSTEM PARTNER Usage metering, anomaly detection, and real-time webhooks for API intelligence. Tracks settlement volume and agent activity patterns. [drippay.dev β†’](https://drippay.dev) πŸ—οΈ ## Infrastructure & programs C ### Circle Alliance ECOSYSTEM PARTNER Official Circle Alliance member. USDC, EURC, and EURCV stablecoin rails for settlement and cross-border payments. [Circle directory β†’](https://partners.circle.com/partner/asterpay) πŸ€– ## Agent platforms & distribution O ### ClawHub (OpenClaw) ECOSYSTEM PARTNER Published AsterPay MCP skill for OpenClaw and agent registries. Enables one-click agent access to trust scoring and settlement. [clawhub.ai β†’](https://clawhub.ai) x ### x402 Bazaar (Coinbase CDP) ECOSYSTEM PARTNER Marketplace listing for x402-paid AsterPay APIs. Agents discover and pay for settlement services through the Coinbase Developer Platform. [Coinbase x402 Bazaar β†’](https://docs.cdp.coinbase.com/x402/bazaar) I ### Invoica ECOSYSTEM PARTNER Financial OS for AI agents. x402-native invoicing, multi-jurisdiction tax (12 countries including EU VIES), and on-chain settlement detection across Base, Polygon, Arbitrum, and Solana. [invoica.ai β†’](https://www.invoica.ai/) ## AsterPay on public registries [πŸ›’ Coinbase x402 Bazaar](https://docs.cdp.coinbase.com/x402/bazaar) [πŸ•·οΈ Apify Store](https://apify.com/petteridev/agent-readiness-checker) [πŸ™ GitHub](https://github.com/aelira-labs) [πŸ“¦ npm @asterpay](https://www.npmjs.com/org/asterpay) [πŸ’œ Circle Alliance](https://partners.circle.com/partner/asterpay) [AsterPay](/) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Privacy](/privacy/) [Terms](/terms/) [𝕏 Twitter](https://x.com/Asterpayment) [Telegram](https://t.me/asterpaycommunity) Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus --- # ERC-8004 Integration | AsterPay - Trust Layer for AI Agents Source: Markdown mirror: > AsterPay is integrating ERC-8004 Trustless Agents standard. The first platform where AI agents build trust, earn money, and receive euros. [← Back to AsterPay](/) πŸ” Live β€” Agent #16850 on Base # ERC-8004 Agent Identity Integration The first platform where AI agents build trust, earn money, and receive euros. AsterPay implements the ERC-8004 Trustless Agents standard and is registered on-chain as Agent #16850 on Base. ## The Complete AI Agent Stack AI agents need four layers to operate autonomously. AsterPay is building all four. πŸ” #### Trust Layer "Who can I trust?" ERC-8004 πŸ’Έ #### Payment Layer "How do I pay?" x402 Protocol πŸ’Ά #### Settlement Layer "How do I get euros?" EUR Off-Ramp πŸ‡ͺπŸ‡Ί #### Compliance Layer "Is this legal in EU?" MiCA-Aligned ## What is ERC-8004? ERC-8004 (Trustless Agents) is an Ethereum standard published in August 2025 that creates a trust layer for autonomous AI agents. It defines three on-chain registries: πŸ†” #### Identity Registry ERC-721 NFT-based identity for each agent. Points to off-chain Agent Card with capabilities and endpoints. ⭐ #### Reputation Registry On-chain feedback system with scores (0-100) and proofOfPayment linking reputation to real transactions. βœ… #### Validation Registry Third-party validation interface supporting stake-based, zkML, and TEE oracle verifications. ### Why ERC-8004 + x402? ERC-8004 is explicitly designed to complement the x402 payment protocol. The standard defines a `proofOfPayment` field that stores x402 transaction hashes, linking every payment to reputation. Real money = real trust. ## AsterPay Integration When we integrate ERC-8004, every AI agent using AsterPay will be able to: - Register on-chain identity β€” ERC-8004 Agent NFT with verifiable history - Build reputation from transactions β€” Every x402 payment updates reputation with proofOfPayment - Get discovered by other agents β€” Searchable registry of trusted agents - Cash out to EUR β€” USDC earnings to SEPA Instant bank transfers ## Competitive Landscape No competitor combines all four capabilities for the European market: | | Capability | AsterPay | PayAI | Coinbase | BVNK | x402 Facilitator | βœ“ | βœ“ | βœ“ | βœ— | EUR Off-Ramp | βœ“ | βœ— | βœ— | βœ“ | ERC-8004 Support | βœ“ Building | ? | ? | βœ— | MiCA-Aligned | βœ“ | βœ— | βœ“ | βœ“ ## Roadmap Q1 2026 #### Research & Builder Program Deep spec analysis, ERC-8004 Builder Program application, technical PoC planning Q2 2026 #### Identity Integration Deploy Identity Registry on Base Sepolia, Agent Registration API, IPFS Agent Cards Q3 2026 #### Reputation Integration x402 β†’ Reputation webhook, proofOfPayment implementation, beta testing Q4 2026 #### Production Launch Mainnet deployment (Base, Polygon), public API, agent discovery features ## ERC-8004 Resources - EIP Specification: [eips.ethereum.org/EIPS/eip-8004](https://eips.ethereum.org/EIPS/eip-8004) - Official Website: [8004.org](https://8004.org) - Builder Program: [8004.org/builder-program](https://8004.org/builder-program) - πŸ—ΊοΈ Ecosystem Map: [8004tokens.xyz/ecosystem](https://www.8004tokens.xyz/ecosystem) AsterPay Listed! - GitHub: [github.com/ethereum/ERCs/pull/1170](https://github.com/ethereum/ERCs/pull/1170) ### Backers & Supporters ERC-8004 is supported by major players in the Ethereum ecosystem: - Ethereum Foundation β€” Created dedicated dAI (Decentralized AI) team - MetaMask β€” Marco De Rossi (AI Lead, co-author) - Coinbase β€” Erik Reppel (co-author) - Google β€” Jordan Ellis (co-author) - Partners β€” ENS, EigenLayer, The Graph, Taiko ### Interested in ERC-8004 + AsterPay? We're actively building the Trust + Payment + Settlement stack for AI agents in Europe. [Get in Touch](mailto:petteri@asterpay.io) [Read the Docs](/docs/) Last updated: January 2026 | [AsterPay](/) --- # x402 EUR settlement for Vercel eve agents β€” AsterPay template | AsterPay Source: Markdown mirror: > Give any Vercel eve agent the ability to pay x402 services in USDC and settle counterparties in EUR via SEPA Instant, with a KYA trust check before paying. Drop-in eve connection + tools template by AsterPay. [← AsterPay](/) Integration Β· Vercel eve # x402 EUR settlement for Vercel eve agents By Petteri , Co-founder of AsterPay Β· Updated: 28 June 2026 In one line: eve gives an AI agent a runtime; AsterPay gives it the ability to pay x402 services in USDC, settle the counterparty in euros (EUR) via SEPA Instant, and check the counterparty's trust (KYA) before paying . Drop the [`asterpay-agent`](https://github.com/petteri74dev/asterpay-agent) template into any eve project and your agent can pay and get paid in real euros. ## Why this exists [eve](https://github.com/vercel/eve) is Vercel's filesystem-first framework for building AI agents. Every agent built on it that pays for a service needs a payment rail β€” and the merchant on the other side usually wants euros in a bank account , not stablecoins on a chain. AsterPay is the layer that closes that gap: it settles USDC/EURC to EUR via SEPA Instant, and it is the only one that scores the counterparty's trust before money moves . ## What the template adds | | Surface | File | What it does | Connection (read-only) | `connections/asterpay.ts` | AsterPay's hosted MCP tools (trust check, settlement estimate, merchant resolve, market rates). No API key. The model never sees a URL or credential. | KYA tool | `tools/asterpay_kya.ts` | Free 0-100 trust score for any wallet / ERC-8004 id. The differentiator. | Quote tool | `tools/asterpay_quote.ts` | Free USDCβ†’EUR settlement estimate, with the fee. | Pay tool | `tools/asterpay_pay.ts` | x402 payment in USDC, gated by human approval above a USDC ceiling. Counterparty settles to EUR. | Skill | `skills/eur-settlement.md` | Playbook: when to KYA, thresholds, fee math. ## The connection β€” read-only AsterPay tools, no API key One file exposes AsterPay's hosted MCP tools to the model. eve brokers auth; the model only discovers tools via `connection_search` and never sees a URL or credential. ``` // agent/connections/asterpay.ts import { defineMcpClientConnection } from "eve/connections"; export default defineMcpClientConnection({ url: process.env.ASTERPAY_MCP_URL ?? "https://mcp-api.asterpay.io/mcp", description: "AsterPay: trust, discovery and EUR-settlement layer for AI agent commerce. " + "Read-only KYA trust score, USDC-to-EUR estimate, merchant resolve, market rates.", tools: { allow: ["check_agent_trust", "settlement_estimate", "merchant_resolve", "market_rates"] }, }); ``` ## The KYA tool β€” check trust before paying ``` // agent/tools/asterpay_kya.ts import { defineTool } from "eve/tools"; import { z } from "zod"; const API = process.env.ASTERPAY_API_URL ?? "https://x402.asterpay.io"; export default defineTool({ description: "Look up an agent/wallet KYA Trust Score (0-100) before transacting. Free, read-only.", inputSchema: z.object({ address: z.string().min(1) }), async execute({ address }) { const res = await fetch(`${API}/v1/agent/trust-score/${encodeURIComponent(address)}`, { headers: { accept: "application/json" } }); if (!res.ok) return { ok: false, status: res.status }; return { ok: true, ...(await res.json()) }; }, }); ``` ## The pay tool β€” x402 in USDC, EUR out, approval-gated Money movement is authored as a native tool so it can sit behind eve's `approval` gate. Note: the property is `approval` (with helpers `once()/always()/never()` or a policy), not `needsApproval`. ``` // agent/tools/asterpay_pay.ts import { defineTool } from "eve/tools"; import { z } from "zod"; import { wrapFetchWithPayment, x402Client } from "@x402/fetch"; import { registerExactEvmScheme } from "@x402/evm/exact/client"; import { privateKeyToAccount } from "viem/accounts"; const MAX_AUTO_USDC = Number(process.env.ASTERPAY_MAX_AUTO_USDC ?? "50"); export default defineTool({ description: "Pay an x402 resource in USDC; counterparty settles in EUR via SEPA Instant.", inputSchema: z.object({ url: z.string().url(), maxUsdc: z.number().positive(), settleEurTo: z.string().optional(), }), approval: ({ toolInput }) => (toolInput?.maxUsdc ?? 0) > MAX_AUTO_USDC ? "user-approval" : "not-applicable", async execute({ url }) { const signer = privateKeyToAccount(process.env.ASTERPAY_AGENT_PRIVATE_KEY as `0x${string}`); const client = new x402Client(); registerExactEvmScheme(client, { signer }); const payFetch = wrapFetchWithPayment(fetch, client); const res = await payFetch(url); return { ok: res.ok, status: res.status, paymentResponse: res.headers.get("x-payment-response") }; }, }); ``` ## Install Clone the open-source template ([github.com/petteri74dev/asterpay-agent](https://github.com/petteri74dev/asterpay-agent), MIT): ``` git clone https://github.com/petteri74dev/asterpay-agent cd asterpay-agent cp .env.example .env # set ASTERPAY_AGENT_PRIVATE_KEY npm install npm run dev ``` Or drop the `connections/`, `tools/` and `skills/` files into an existing eve project (`npx eve@latest init my-agent`). ## Security model AsterPay is non-custodial : the agent signs its own USDC payments, and EUR settlement runs through a licensed EU partner β€” AsterPay never holds the funds. The signing key lives only inside the eve tool's `execute` sandbox as an encrypted env var, never in `instructions.md` and never in model context. For production, use a session key or smart account with an on-chain spend cap and keep the approval gate on. ## Pricing - Read-only (KYA, quote, discovery): free, no signup. - EUR settlement: 0.5% + €0.10 per settled transaction (plus the partner spread shown in the quote). - x402 API calls: $0.001-0.10 per call, paid in USDC. ### Try a KYA trust score right now No signup, no key. Read-only and live in production. [Open a live trust score β†’](https://x402.asterpay.io/v1/agent/trust-score/0xF9035b2643EFa7266805219719971fFC7aC88170) PL Petteri Co-founder of AsterPay (AELIRA LTD). Building the EU-native trust + EUR-settlement layer for AI agent commerce. [@Asterpayment](https://x.com/Asterpayment) ## Related - [asterpay-agent template on GitHub (MIT)](https://github.com/petteri74dev/asterpay-agent) - [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - [What is KYA (Know Your Agent)?](/learn/what-is-kya/) - [AsterPay FAQ](/faq/) - [eve β€” the framework for building agents](https://github.com/vercel/eve) --- # AsterPay FAQ β€” AI agent payments, EUR settlement, MCP & x402 | AsterPay Source: Markdown mirror: > Frequently asked questions about AsterPay: what it is, which blockchains and stablecoins it supports, how the MCP server works, x402, KYA trust scoring and EUR settlement via SEPA Instant for AI agents. [← AsterPay](/) # Frequently asked questions What AsterPay is, the chains and stablecoins it supports, how its MCP server works, and how AI agents settle stablecoins to euros via SEPA Instant. ## What is AsterPay and how does it work? AsterPay is the trust, discovery and EUR-settlement layer for AI agent commerce. It lets AI agents pay for services over open payment protocols ([x402](/learn/what-is-x402/) and MPP) in stablecoins, and lets the merchant on the other side receive the money as euros (EUR) in a bank account via SEPA Instant, typically in under 10 seconds. AsterPay is non-custodial: the regulated EUR settlement is executed by a licensed EU partner, and AsterPay never holds client funds. ## Which blockchains and stablecoins does AsterPay support? AsterPay settles the stablecoins USDC, EURC and EURCV on five EVM chains: Base (primary), Ethereum , Arbitrum , Polygon and Optimism . Bitcoin Lightning is supported for sub-cent micropayments. Additional chains such as Solana and XRPL are on the roadmap. ## What is the Model Context Protocol (MCP) and how does AsterPay use it? The Model Context Protocol (MCP) is an open standard that lets AI models (such as Anthropic Claude, OpenAI GPT and Google Gemini) talk directly to external data sources and tools. AsterPay provides a hosted MCP server (and the `@asterpay/mcp-server` npm package) so AI agents can check an agent's trust score, discover merchant payment details, get a USDC-to-EUR settlement quote and initiate x402 payments directly, without complex integration code. The read-only tools require no API key. ## What is x402 and does AsterPay support it? x402 is an open payment protocol that uses the HTTP 402 "Payment Required" status code so an API can request an on-chain stablecoin payment from an AI agent in a single round trip. AsterPay is an [x402 facilitator](/learn/what-is-an-x402-facilitator/): it verifies the payment and settles it. AsterPay also supports MPP (the Machine Payments Protocol) on every paid endpoint, so agents on either standard can pay. ## What is KYA (Know Your Agent)? [KYA](/learn/what-is-kya/), Know Your Agent, is AsterPay's trust layer for autonomous agents. It produces a 0-100 Trust Score for a wallet or ERC-8004 agent identity, combining on-chain identity, sanctions screening and wallet behavior, so a counterparty can decide whether to transact before money moves. The trust-score endpoint is free and read-only. ## How fast and how expensive is EUR settlement with AsterPay? End-to-end settlement from a stablecoin payment to euros in a bank account is typically under 10 seconds via SEPA Instant, which runs 24/7/365 across the EU/EEA. AsterPay charges 0.5% + €0.10 per settled transaction on the EU rail (plus the licensed partner's spread, shown transparently in the quote). Read-only calls such as trust scores and settlement estimates are free. ## Is AsterPay regulated, and does it hold customer funds? AsterPay is non-custodial and does not hold customer funds. The regulated activity (the stablecoin-to-EUR conversion and SEPA payout) is executed by a licensed EU partner under that partner's authorization. AsterPay operates as the technology and agent layer on top, providing trust scoring, discovery, routing and the developer integration. ## How do AI agents integrate AsterPay? Four ways: the hosted MCP server (no API key) for any MCP-capable agent; the Python SDK (`pip install asterpay`); the [eve agent template](/eve/) for Vercel eve agents; and the direct HTTP API at `x402.asterpay.io` with free read-only endpoints for trust scores and settlement estimates. ### Try it without signing up Get a USDCβ†’EUR settlement estimate. No key, no account. [Estimate $100 β†’ EUR β†’](https://x402.asterpay.io/v1/settlement/estimate?amount=100) --- # Make your store agent-payable β€” AsterPay Fix-Pack Source: Markdown mirror: > One payment. We make your site discoverable and payable by AI agents, and wire EUR settlement to your bank. Pay by card or x402. [AsterPay](https://asterpay.io/) [← asterpay.io](https://asterpay.io/) # Get paid in EUR by AI agents Settled to your bank, often the same day. We make your store discoverable and payable by AI agents with one payment, no card rails. Why now: MiCA clarity is live and agents are choosing which merchants they can transact with. Be discoverable first. 0.5% + €0.10 per settlement vs ~2.9% cards EUR in under 10s Live on Base MiCA-aligned Built on live infrastructure: [x402.asterpay.io](https://x402.asterpay.io/health) Β· listed on [x402scan](https://www.x402scan.com/) Β· ERC-8004 Agent #16850 on Base Β· Circle Alliance member GOOD Β· GET FOUND €49 one-time Want to be found and quoted by AI agents now, and add EUR settlement later? Start here. - βœ“ agent.json, llms.txt, x402.json & pay.json generated for your domain - βœ“ x402 + MPP payment endpoints pre-declared so agents know how to pay - βœ“ Discoverable to AI agents and x402 directories (x402scan) - βœ“ Works alongside your existing checkout β€” nothing to rip out - βœ“ Copy-paste ready, emailed to you in minutes - βœ“ Upgrade to full EUR settlement whenever you're ready Get found by agents β€” €49 β†’ For teams that want to be discoverable and quotable first, settlement later. Most popular BEST Β· DONE-FOR-YOU €199 one-time Get paid in EUR by AI agents, settled to your bank. We set up everything; you complete one short form. - βœ“ USDC/EURC β†’ EUR in your bank in under 10s via SEPA Instant - βœ“ 0.5% + €0.10 per settlement vs ~2.9% typical card rails. No monthly fee, no lock-in - βœ“ We deploy everything for you + send your KYB link (one short form) - βœ“ KYA trust + Chainalysis sanctions screening on every paying agent - βœ“ Founder support to your first live euro Technical details β–Ύ - βœ“ Everything in Get Found (agent.json, llms.txt, x402.json & pay.json) - βœ“ Dual protocol accepted: x402 (Coinbase) + MPP (Stripe/Tempo) - βœ“ VoP (PSD2) payee verification on your payout account - βœ“ Accept on Base, Ethereum, Polygon, Arbitrum & Optimism On €10k/mo in agent payments: ~€50 with AsterPay vs ~€290 on typical card rails. Get paid in EUR β€” €199 β†’ Most setups go live within a day. ↩ Capability guarantee: if we can't make your site able to receive an agent payment, you get a full refund. Agents & developers: pay with x402 (USDC on Base) β–Ύ Prefer to pay from an agent wallet? Pick a plan, send the exact USDC amount on Base to the address below, then paste the transaction hash. We verify it on-chain and fulfil instantly β€” no card, no signup. Get Found β€” 49 USDC Done-for-you β€” 199 USDC Pay to: `loading…` on Base (USDC) Verify payment & deliver β†’ Checkout canceled β€” nothing was charged. Pick a plan whenever you're ready. Setup is a one-time payment. After go-live there are no monthly fees: just 0.5% + €0.10 per EUR settlement, no card rails, no lock-in. Questions? [petteri@asterpay.io](mailto:petteri@asterpay.io) Β· AELIRA LTD Β· Cyprus --- # AI Agent Payments for Marketplaces β€” EUR Settlement | AsterPay Source: Markdown mirror: > Let AI agents buy from your marketplace and pay sellers in EUR. AsterPay scores every payer (KYA), accepts x402 and MPP, and settles to seller IBANs via SEPA Instant. [AsterPay](/) [Home](/) [Home](/) β€Ί For Marketplaces For Marketplaces # AI agents buy. Your sellers get paid in EUR. When the buyer is an autonomous agent, your marketplace needs three things at once: accept the payment, trust the payer, and pay each seller in real money. AsterPay does all three β€” agents pay in USDC over x402 or MPP, every payer is scored with KYA, and EUR settles to each seller's IBAN via SEPA Instant. [Run a free readiness check](/) [Read the docs](/docs/) ## From agent checkout to seller payout One flow handles acceptance, trust and EUR settlement β€” your marketplace never touches crypto custody. 01 ### Agent pays at checkout The agent pays in USDC over x402 or MPP. AsterPay scores the payer 0-100 on identity, wallet history and sanctions (KYA) before anything settles. 02 ### Resolve the seller The Merchant Payment Endpoint resolves and validates each seller's verified IBAN/BIC from provable sources, with logged provenance. 03 ### EUR to each seller Settlement routes EUR to each seller's bank via SEPA Instant in under 10 seconds, through licensed European payment partners. 0.5% + €0.10 per payout. ## Why marketplaces use AsterPay ### Trust scoring on every payer Set a minimum KYA tier to allow, hold or block an agent payment. Fraud control before settlement, not after a chargeback. ### Split payouts to many sellers Resolve and validate each payee, then settle EUR to every seller's IBAN. Resolution is free; settlement is 0.5% + €0.10 per payout. ### No crypto custody for you Funds route through licensed PSP/CASP partners on a non-custodial architecture. AsterPay is the technical and trust layer. ### EU-native, MiCA-aligned Settlement runs under partners' MiCA, EMI and PSD2 authorisations. EUR via SEPA Instant today; GBP and USD on the roadmap. ## Marketplace FAQ How do AI agents pay sellers on a marketplace through AsterPay? An agent pays in USDC over x402 or MPP at checkout. AsterPay scores the payer with KYA, resolves each seller's verified payment details through the Merchant Payment Endpoint, and settles EUR to the seller's IBAN via SEPA Instant. The marketplace never has to touch crypto custody. Can AsterPay pay multiple sellers from one agent order? Yes. The Merchant Payment Endpoint resolves and validates each payee, then settlement routes EUR to each seller's IBAN via SEPA Instant. Resolution is free; settlement is 0.5% + €0.10 per payout. How does AsterPay reduce fraud from autonomous agents? Every paying agent is scored 0-100 on identity (ERC-8004), wallet history and sanctions screening (KYA) before settlement. Marketplaces can set a minimum trust tier to allow, hold or block a payment. What currencies can sellers receive? EUR via SEPA Instant is live today, in under 10 seconds. GBP via Faster Payments and USD via ACH are on the roadmap (Q4 2026). ## Make your marketplace agent-payable Run a free readiness check to see what an AI agent needs to pay across your marketplace β€” then go live in minutes. [Run the free check](/) [AsterPay](/) Β· [Docs](/docs/) Β· [For SaaS & APIs](/for-saas/) Β· [Learn](/learn/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # AI Agent Payments for SaaS & APIs β€” Get Paid in EUR | AsterPay Source: Markdown mirror: > Make your SaaS or API agent-payable. AI agents pay per call in USDC via x402 or MPP; AsterPay settles real euros to your bank via SEPA Instant. No card, no checkout. [AsterPay](/) [Home](/) [Home](/) β€Ί For SaaS & APIs For SaaS & APIs # Let AI agents pay your API. Get EUR in your bank. Shoppers and integrations are becoming AI agents. Make any SaaS endpoint or API agent-payable: agents pay per call in USDC over x402 or MPP, and AsterPay settles real euros to your IBAN via SEPA Instant β€” in under 10 seconds, no card, no checkout, no human in the loop. [Run a free readiness check](/) [Read the docs](/docs/) ## Go live in three steps No new merchant account, no card-network onboarding. If you can return an HTTP header, you can get paid by agents. 01 ### Gate your endpoint Return HTTP 402 with an x402 payment header pointing to AsterPay. Every 402 carries both x402 and MPP headers, so agents use whichever SDK they already have. 02 ### Agent pays per call The agent pays in USDC on Base, Polygon, Arbitrum, Optimism or Ethereum. AsterPay scores the payer (KYA) and verifies the payment before your resource is served. 03 ### You receive EUR AsterPay settles to your bank in EUR via SEPA Instant in under 10 seconds, through licensed European payment partners. 0.5% + €0.10 per payout. ## Why SaaS teams use AsterPay ### Pay-per-call, no minimums Charge $0.001 to $0.10 USDC per call. No subscription, no token, no minimum volume β€” meter exactly what an agent consumes. ### EUR in the bank, not USDC on a wallet The last mile is the hard part. AsterPay closes it: stablecoins in, euros out to your IBAN, reconciled with a signed receipt. ### Trust before settlement (KYA) Every payer is scored 0-100 on identity (ERC-8004), wallet history and sanctions screening before a cent settles. ### Non-custodial, MiCA-aligned Funds route through licensed PSP/CASP partners, not AsterPay's balance sheet. AsterPay is the technical and trust layer. ## SaaS & API FAQ How do I make my SaaS or API accept AI agent payments? Return HTTP 402 with an x402 payment header pointing to AsterPay. The agent pays in USDC on Base, Polygon, Arbitrum, Optimism or Ethereum, AsterPay verifies and settles, and you receive EUR via SEPA Instant. Every 402 response also carries an MPP header, so agents can use either SDK. What does it cost? Free endpoints (KYA trust score, settlement estimate, merchant resolve) require no payment. Paid API calls cost $0.001 to $0.10 USDC per call via x402 or MPP. EUR settlement costs 0.5% + €0.10 per payout. No subscription, no token, no minimum volume. Is AsterPay custodial? No. AsterPay operates a non-custodial architecture; customer funds route through licensed European payment partners (PSP/CASP), not through AsterPay's balance sheet. Settlement is performed by the licensed partner under their MiCA, EMI and PSD2 authorisations. What currencies can I settle to? EUR via SEPA Instant is live today, in under 10 seconds. GBP via Faster Payments and USD via ACH are on the roadmap (Q4 2026). ## Make your API agent-payable Run a free readiness check to see what an AI agent needs to pay you β€” then go live in minutes. [Run the free check](/) [AsterPay](/) Β· [Docs](/docs/) Β· [For marketplaces](/for-marketplaces/) Β· [Learn](/learn/) Β· [@Asterpayment](https://x.com/Asterpayment) Β© 2026 AsterPay (AELIRA LTD) --- # AsterPay β€” let AI agents pay you, get EUR in your bank | x402 + MPP Β· SEPA Instant Source: Markdown mirror: > EUR-native facilitator for AI agent payments. x402 (Coinbase) and MPP (Stripe/Tempo), USDC to EUR via SEPA Instant. KYA trust scoring, MiCA-aligned. Check your site in 60 seconds, then make it agent-payable. [AsterPay](#top) Products Solutions Developers [Pricing](#pricing) [Sign in](https://app.asterpay.io/login)[Get started](https://app.asterpay.io/signup) I sell products I build agents # Let AI agents pay you.Get EUR in your bank. [Check your store β†’](#check)[See how it works](#flow) Live on Base Β· agents are already paying Β· EUR in under 10s Β· fast KYB Facilitator free forever Β· x402 verify & settle: $0, no API key Β· you pay only when euros hit your bank (0.5% + €0.10) Β· [Compare fees β†’](/learn/x402-facilitator-fees-compared/) Agent-readiness check ### Enter your site. See what agents see. See if AI agents can find and buy from you. Free, no signup, public files only. Your website or API domain Run free check β†’ Circle Alliance SEPA Instant MiCA-aligned ERC-8004 Intuition InsumerAPI Invoica x402 Bazaar Drip ClawHub GitHub Circle Alliance SEPA Instant MiCA-aligned ERC-8004 Intuition InsumerAPI Invoica x402 Bazaar Drip ClawHub GitHub ## From agent payment to euros in your bank. 01 ### Accept An agent pays your API in USDC over x402 or MPP. No card, no checkout, no human in the loop. β†’ 02 ### Verify KYA scores every payer on identity, sanctions and wallet history. Bad actors are blocked before settlement. β†’ 03 ### Settle We convert to EUR and send it to your IBAN via SEPA Instant. 0.5% + €0.10. Seconds, not days. Easiest onboarding in payments ## Get paid by AI agents in three steps. No SDK to wire up, no checkout to build, no merchant account. Most stores are agent-payable the same afternoon. [Run the free check β†’](#check)[Book a call](https://www.cal.eu/asterpay) - 1 ### Run the free check Paste your domain. In 5 seconds you see exactly where AI agents can't find or pay you. No signup, no card. - 2 ### Hand the fix to your AI agent Copy the tailored prompt into Cursor, Claude Code or Copilot β€” or let us ship it for you. No engineering work on your side. - 3 ### Go live, get paid in EUR Connect AsterPay. Agents pay in stablecoins, you receive euros in your bank via SEPA Instant. 0.5% + €0.10 per payout. The receipt ## This is what lands in your account. 9:41 Business Β· EUR Operating account Payment received +€91.44 from Agent Β· order #A1F4 Paid in 100.00 USDC Route USDC β†’ EUR Rail SEPA Instant Β· 8.4s Settled to IBAN β€’β€’1234 Settled reconciled Β· signed receipt x402 gets agents to pay. AsterPay gets you paid in EUR. The protocols move stablecoins between machines. We turn that into money in a European bank account, with the trust and compliance layer agents do not bring with them. ## You only pay when you get paid. Facilitator free forever ### x402 verify & settle costs $0. Forever. Verifying and settling x402 payments on-chain is free at AsterPay, same as at Coinbase CDP. No API key, no monthly fee, no volume tiers. We charge only on the value layer: EUR in your bank (0.5% + €0.10), KYA trust screening and premium API calls. [Compare facilitator fees β†’](/learn/x402-facilitator-fees-compared/) $0 verify (x402 + MPP) $0 settle USDC on-chain $0 API key β€” there is none ### EUR settlement 0.5% + €0.10 per payout 1.5% + €1.00 on the US rail - Nothing before you go live - SEPA Instant payout to your IBAN - Free done-for-you setup - No subscription, no card ### Developer API $0.001 to $0.10 USDC per call Pay-per-call via x402 or MPP - No API key required - KYA trust score + merchant resolve - Settlement estimates and market rates - Keyless, metered, no minimums Heavy, predictable agent traffic? [See AsterPay Subscriptions](/subscriptions/) β€” one flat monthly price for unlimited agent verification and routing. ## Questions agents and builders ask. What is AsterPay? AsterPay is the EUR settlement layer for AI agent payments. It is an x402 facilitator that converts USDC, EURC and EURCV stablecoins from five EVM chains (Base, Ethereum, Polygon, Arbitrum, Optimism) to EUR via SEPA Instant in under 10 seconds, with settlement performed by licensed European payment partners. GBP via Faster Payments and USD via ACH are on the roadmap (Q4 2026). How do I accept x402 payments in euros? Use AsterPay as your x402 facilitator and EUR settlement endpoint. Your API returns HTTP 402 with an x402 payment header pointing to AsterPay; the agent pays in USDC on Base, Polygon, Arbitrum, Optimism or Ethereum, and AsterPay pays you EUR via SEPA Instant. KYB onboarding takes 10 minutes through Sumsub. No per-transaction KYC, no manual off-ramp. What is an x402 facilitator? An x402 facilitator is the trusted party that verifies and settles a HTTP 402 payment. It checks the payment proof, executes the on-chain settlement, and forwards the result to the resource server. Coinbase CDP runs the default facilitator on Base. AsterPay runs an EU-native facilitator that adds EUR settlement (via licensed European payment partners), KYA trust scoring and ERC-8004 identity attestation on top of the standard x402 flow. How do I convert USDC to EUR for AI agents? Send USDC to AsterPay's settlement endpoint and we convert it to EUR via licensed CASP partners and pay your bank account through SEPA Instant. AsterPay supports USDC, EURC and EURCV on Base, Polygon, Arbitrum, Optimism and Ethereum. End-to-end latency is under 10 seconds. What is KYA (Know Your Agent)? KYA (Know Your Agent) is AsterPay's open trust-scoring framework for AI agents in payment flows. It scores any agent wallet 0-100 from seven signals organised in a 4-layer framework (Identify, Screen, Settle, Comply): wallet age, wallet activity, sanctions screening, ERC-8004 identity, operator KYB, payment history and trust bond. KYA is the agent-payments equivalent of KYC for humans. How does AsterPay compare to Stripe for AI agent payments? Stripe is built for human checkout flows; AsterPay is built for autonomous AI-agent payments. Stripe requires merchant accounts, card-network fees and 2-7 day settlement. AsterPay accepts stablecoin payments via x402 and MPP, settles to EUR via SEPA Instant in under 10 seconds, and includes KYA trust scoring. Use Stripe if your customer is a human; use AsterPay if your customer is an AI agent. How do I integrate AsterPay? Three ways: (1) MCP server β€” npm install @asterpay/mcp-server β€” for any LLM agent that speaks MCP. (2) Python SDK β€” pip install asterpay β€” for Python agents. (3) Direct HTTP API at x402.asterpay.io for any language. Free endpoints (KYA trust score, settlement estimate) require no auth. Paid endpoints accept either x402 or MPP payment proofs. Full docs at asterpay.io/docs. What payment protocols does AsterPay support? AsterPay accepts two payment protocols on every paid endpoint: x402 (Coinbase HTTP-402 standard, plus the x402r escrow/refund extension) and MPP / Machine Payments Protocol (Stripe and Tempo open standard) β€” every 402 response includes both header sets, so agents use whichever SDK they already have. On top of these, AsterPay is compatible with AP2 (Google Agent Payments) and A2A for agent coordination, and uses ERC-8004 for on-chain agent identity. What chains and stablecoins does AsterPay accept? AsterPay accepts stablecoin payments on five EVM chains with native USDC: Base, Polygon, Arbitrum, Optimism and Ethereum. Supported stablecoins include USDC, EURC and EURCV. Bitcoin Lightning is also live for sub-cent micropayments. All payments settle to EUR via SEPA Instant today; GBP (Faster Payments) and USD (ACH) settlement is on the roadmap (Q4 2026). Is AsterPay regulated in the EU? AsterPay operates through AELIRA Ltd (EU entity) and is built on a non-custodial architecture: customer funds never touch AsterPay's balance sheet. Off-ramps run through licensed CASP partners under MiCA, with KYB onboarding via Sumsub. AsterPay operates as a technical service provider; settlement is performed by licensed European payment partners under their MiCA, EMI and PSD2 authorisations. How much does AsterPay cost? Free endpoints (KYA trust score, settlement estimate, merchant resolve, market data) require no payment or auth. Paid API endpoints cost $0.001 to $0.10 USDC per call via x402 or MPP. EUR settlement costs 0.5% + €0.10 per settled transaction on the EU rail. No subscription, no token, no minimum volume. How does an AI agent pay a business when it only knows the company name? Through AsterPay's Merchant Payment Endpoint (MPE). The agent sends the company name or VAT number to GET /v1/mpe/merchants/resolve, which resolves the payee only from provable sources and returns the IBAN/BIC with logged provenance and a confidence level. Full IBAN validation runs on every resolve; bank-side PSD2 Verification of Payee is performed by the licensed settlement PSP before payout. POST /v1/mpe/settle then chains resolve, payee validation, KYA trust check, USDC-to-EUR conversion and SEPA Instant payout in one call. Resolution is free. Does AsterPay have a native token? No. AsterPay has no native token, no on-chain governance, no airdrop, no presale, and no plans for any of these. Customers pay in USDC, EURC, EURCV or fiat. There is no $ASTERPAY, $ASTER, or any other AsterPay-issued token in existence or in the roadmap. Is AsterPay related to Aster (ASTER) DEX, AstroPay or AstraPay? No. AsterPay by AELIRA LTD (Cyprus, HE 490977) is AI-agent payment trust and EUR settlement infrastructure on the x402 (Coinbase) and MPP (Stripe/Tempo) protocols. It is not affiliated with Aster (ASTER) DEX (the BNB Chain perpetual exchange), with AstroPay (the consumer digital wallet), or with AstraPay (the Indonesian payment service). AsterPay has no native token, no $ASTER, no on-chain governance, and no presence on BNB Smart Chain. [AsterPay](#top) Financial infrastructure for the agentic economy. EU-native, EUR-native. Built for MiCA. ##### Product - [x402 facilitator](/learn/what-is-an-x402-facilitator/) - [ClinPay](/clinpay/) - [KYA trust scoring](/learn/what-is-kya/) - [Subscriptions](/subscriptions/) - [Pricing](#pricing) - [Compare](/compare/) - [Facilitator fees](/learn/x402-facilitator-fees-compared/) ##### Developers - [Try the API free](/try/) - [Integrations](/new/integrations/) - [Docs](/docs/) - [API reference](/docs/) - [GitHub](https://github.com/aelira-labs) - [MCP server](https://www.npmjs.com/package/@asterpay/mcp-server) - [agent.json](/.well-known/agent.json) - [llms.txt](/llms.txt) - [Coinbase Bazaar check](/bazaar) ##### Company - [Learn hub](/learn/) - [Ecosystem](/ecosystem/) - [Partners](/partners/) - [Trust Center](/trust/) - [Blog](/blog/) - [Book a call](https://www.cal.eu/asterpay) - [Contact](/contact/) ##### Social - [@Asterpayment](https://x.com/Asterpayment) - [Telegram](https://t.me/petterixai) Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus [Privacy](/privacy/)[Terms](/terms/)[Security](/security/)[Trust Center](/trust/) The score is a metadata check of public files, not a certification. AsterPay is non-custodial and settles EUR through licensed EU SEPA partner rails. Built for MiCA, live payout requires KYB. AsterPay is not affiliated with Aster (ASTER) DEX, AstroPay or AstraPay; it has no native token and no presence on BNB Smart Chain. --- # AsterPay as a MiCA-aligned arbiter for Circle's Refund Protocol | AsterPay Source: Markdown mirror: > Circle [← Learn hub](/learn/) # AsterPay as a MiCA-aligned arbiter for Circle's Refund Protocol Published 3 May 2026 Β· 7 minute read Β· By Petteri Leinonen, Co-founder Short answer Circle's Refund Protocol gives stablecoin payments the missing chargeback primitive without putting any party in custody of the funds. The smart contract is finished; the arbiter slot is open. AsterPay's position is to operate as a KYA-graded, MiCA-aligned arbiter for x402 and Nanopayments flows where both the payer agent and the recipient merchant have an attestation on file. This page explains the protocol, why the arbiter role matters, and how AsterPay proposes to fill it for European agent commerce. Position statement (3 May 2026) AsterPay endorses Circle's Refund Protocol as the right primitive for non-custodial dispute resolution on ERC-20 stablecoin payments. We are publishing this page as our public position before integration work begins. We expect a competitive arbiter market to emerge over the next two quarters; our intent is to be the EU-native, KYA-graded option for European merchants and the agent platforms that route to them. ## What Refund Protocol actually does Circle Research released the [Refund Protocol smart contract](https://github.com/circlefin/refund-protocol) in 2026, alongside a [technical write-up on the Circle blog](https://circle.com/blog/refund-protocol-non-custodial-dispute-resolution-for-stablecoin-payments) and a community deep-dive on [Arc House](https://community.arc.network/public/forum/boards/circle-products-and-developer-toolings-0iw/posts/the-refund-protocol-how-circle-brought-chargebacks-to-crypto-without-giving-up-custody-tgpiyol1jv). The contract introduces five functions that together form a complete escrow-plus-arbitration surface for any ERC-20 token, USDC included. | | Function | Caller | Effect | `pay(to, amount, refundTo)` | Payer | Locks `amount` in escrow, records `to` as recipient and `refundTo` as the address any refund must return to. Refund address is fixed at payment time. | `refundByRecipient(paymentID)` | Recipient | Voluntary refund to the pre-specified `refundTo`. The merchant's "yes, refund this customer" path. | `refundByArbiter(paymentID)` | Arbiter | Forced refund when the recipient refuses. Deducts from the recipient's escrowed balance; if the recipient has already withdrawn, the arbiter must cover the refund and the contract records a debt owed back to the arbiter from future payments. | `withdraw(paymentID)` | Recipient | Permissionless withdrawal after the lockup period elapses, as long as no refund has been issued. Keeps the contract non-custodial: the arbiter cannot indefinitely block withdrawal. | `earlyWithdrawByArbiter(paymentID)` | Arbiter (with EIP-712 sig) | Recipient signs an off-chain consent specifying a fee paid to the arbiter; the arbiter executes withdrawal before the lockup expires. Protects the recipient from arbitrary fees. The arbiter has exactly three powers: refund to the pre-specified address, allow early withdrawal at a recipient-consented fee, and set the lockup period for new payments. The arbiter cannot redirect funds to a third party, cannot indefinitely block a withdrawal, and cannot increase the locked amount. This is what Circle means by "non-custodial dispute resolution" β€” the contract structurally bounds what the arbiter is permitted to do. ## Why the arbiter slot exists, and why it is open Stablecoin payments to date have been closer to cash than to credit cards: irreversible by default, no recourse if the merchant fails to deliver. That is fine for tipping and capital movement; it is not fine for commerce. Refund Protocol fills the gap with on-chain escrow, and an arbiter is the entity the payer appeals to when the merchant refuses a legitimate refund. Circle deliberately did not name an arbiter inside the contract. The role is configurable per deployment; any address can be set. This is the right design choice because the arbiter requirements are jurisdiction-specific: a US merchant with US customers wants a US-aligned arbiter, a German merchant with EU agent traffic wants an EU-aligned arbiter, an on-chain protocol may want a DAO. Hard-coding a single arbiter would have made the protocol unusable in most regulated markets. That said, an arbiter cannot just be a wallet. To be useful in production it needs: - Identity attestations on both the payer and the recipient, so disputes can be graded against verifiable evidence rather than anonymous claims. - A regulatory posture compatible with the payer and recipient jurisdictions β€” especially if the dispute resolution interacts with consumer-protection law or AML reporting. - Refund-coverage capital , because the contract allows recipients to withdraw early and an arbiter that refunds in those cases is fronting the money until the recipient pays the debt back from future receipts. - An appeal interface β€” an HTTP surface, an SLA, evidence intake, a published policy β€” that is good enough that customers and merchants both consider it fair. None of those are in Circle's GitHub repo. They are the operating model around the contract. ## AsterPay's position on the arbiter role AsterPay's existing trust stack already supplies three of the four requirements above. [KYA (Know Your Agent)](/learn/what-is-kya/) attestations cover the payer side. [ERC-8004](/learn/erc-8004-explained/) on-chain identity covers the agent identity layer. The MiCA-aligned settlement model covers the regulatory posture for EUR flows. Refund-coverage capital is the only new dimension; it is a small balance-sheet line item compared to the trust infrastructure. Concretely, our intent is to operate as an opt-in arbiter for x402 and Nanopayments flows where both ends have a KYA attestation. Disputes are graded against the attestation tier; merchants on higher tiers receive shorter lockup periods and lower arbiter fees. Where a merchant has already withdrawn early and the arbiter must front the refund, the debt is recorded on-chain and offset against future settlement receipts β€” the contract does this automatically. ### What "AsterPay as arbiter" means in practice - Opt-in per merchant. Refund Protocol escrow is not the default x402 behaviour; merchants enable it on routes where chargeback risk matters (high-ticket, novel counterparty, regulated category). - KYA-graded lockup periods. Higher-tier merchants get shorter lockups; new or unattested merchants start at the conservative default and earn shorter lockups over time. - Published dispute policy. Plain-English appeal SLA, evidence categories accepted, indicative timelines. Arbiter decisions are logged on-chain via the contract; reasoning is logged off-chain in the appeal record. - EU-native posture. EUR-denominated refunds, EU consumer-protection grounding, German/French/Spanish/Italian appeal intake on the roadmap. - Non-custodial throughout. AELIRA LTD never takes title to USDC. Refund risk capital is held in EUR on the AsterPay treasury and routed through licensed European payment partners when an actual refund must move. - No CASP licence required for the arbiter role itself. The arbiter signs to release or refund; underlying USDC-to-EUR conversion (when triggered) flows through licensed partners on their own books. ## How this fits the wider Circle stack The picture coming together in 2026 has three layers: - x402 β€” the negotiation protocol. HTTP 402, scheme-agnostic, settled into the Linux Foundation in April 2026 with backing from Google, Stripe and Visa. - Circle Nanopayments β€” the gas-free settlement primitive that runs on top of x402. Live on mainnet across 11 EVM chains as of April 2026 ([Circle blog](https://www.circle.com/blog/nanopayments-powered-by-circle-gateway-is-now-live-on-mainnet)). Sub-cent payments via batched EIP-3009 settlement. - Refund Protocol β€” the dispute-resolution layer that wraps any ERC-20 payment, Nanopayments-settled or otherwise, in non-custodial escrow with an arbiter. None of these are competitive with each other. An x402 request can resolve to a Nanopayments-settled payment, which can be wrapped in a Refund Protocol escrow with AsterPay as arbiter. The whole stack is composable and the trust layer (KYA, attestations, arbitration) is the part that does not commoditise as the settlement primitive does. ## What we are not claiming This is a position paper, not a product launch. Specifically: - We have not yet deployed an arbiter contract on any mainnet. Integration design and capital sizing are the next steps. - Circle has not endorsed AsterPay as an arbiter. The arbiter slot is open by design and we are publishing our intent to occupy it in the EU corridor, alongside whatever arbiters emerge in other jurisdictions. - Refund Protocol does not solve every dispute scenario. It is the right primitive for "merchant did not deliver" and "wrong amount" cases. It does not solve sanctions screening, fraud detection on the payer side, or pure quality disputes that require expert review. - The non-EVM rails AsterPay supports (Lightning, Solana) are not covered by Refund Protocol because the contract is ERC-20-only. Disputes on those rails continue to use AsterPay's existing manual settlement-reversal path. ## What you can do now If you operate a merchant or platform integrating x402 or Nanopayments, three actions are useful this quarter: - Read the [Refund Protocol repo](https://github.com/circlefin/refund-protocol) and decide which routes need escrow. Most x402 calls do not; the high-ticket, slow-fulfilment ones do. - Get a [KYA attestation](/learn/what-is-kya/) on file. It is the input the arbiter (any arbiter, not only AsterPay) will use to grade your disputes. - If you want to be on the early-access list for AsterPay arbiter integration, email [samantha@asterpay.io](mailto:samantha@asterpay.io?subject=Refund%20Protocol%20arbiter%20early%20access) with subject "Refund Protocol arbiter early access". We will publish concrete deployment details and contract addresses once the integration is on testnet. ### Sources - [circlefin/refund-protocol](https://github.com/circlefin/refund-protocol) β€” smart contract source - [Refund Protocol: Non-Custodial Dispute Resolution for Stablecoin Payments](https://circle.com/blog/refund-protocol-non-custodial-dispute-resolution-for-stablecoin-payments) β€” Circle blog - [The Refund Protocol: How Circle Brought Chargebacks to Crypto Without Giving Up Custody](https://community.arc.network/public/forum/boards/circle-products-and-developer-toolings-0iw/posts/the-refund-protocol-how-circle-brought-chargebacks-to-crypto-without-giving-up-custody-tgpiyol1jv) β€” Arc House technical deep-dive - [Nanopayments powered by Circle Gateway is live on mainnet](https://www.circle.com/blog/nanopayments-powered-by-circle-gateway-is-now-live-on-mainnet) β€” Circle blog - [What is x402?](https://developers.circle.com/gateway/nanopayments/concepts/x402) β€” Circle developer docs ### Related guides - [What is KYA (Know Your Agent)?](/learn/what-is-kya/) - [ERC-8004 explained](/learn/erc-8004-explained/) - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - [MiCA-aligned stablecoin settlement](/learn/mica-aligned-stablecoin-settlement/) - [Best x402 facilitator in Europe](/learn/best-x402-facilitator-europe/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay is not affiliated with Aster (ASTER) DEX, the BNB Chain perpetual exchange, and has no native token. Circle, USDC, Circle Gateway and the Refund Protocol are products of Circle Internet Financial; this page describes AsterPay's independent position on operating as an arbiter under the publicly released Refund Protocol smart contract and is not a Circle endorsement. This page is an information document, not legal advice. --- # Best x402 facilitator in Europe β€” how to choose | AsterPay Source: Markdown mirror: > How to choose an x402 facilitator in Europe for AI agent payments. Selection criteria, EU-native vs US-native, EUR settlement, KYA trust, MiCA partner routing, vendor table. [← Learn hub](/learn/) # Best x402 facilitator in Europe β€” how to choose Updated 3 May 2026 Β· 5 minute read Β· By Petteri, Co-founder Short answer Pick a facilitator that settles to EUR via SEPA Instant inside the same HTTP 402 round-trip, names its CASP partners publicly, scores agent trust before paying out, and accepts both x402 and MPP on every endpoint. As of May 2026, AsterPay is the only EU-native x402 facilitator in production that scores yes on all six criteria below. ## What an x402 facilitator does HTTP 402 is the protocol layer. It says "this resource costs N units of asset X on chain Y; here is how to pay." The facilitator is the runtime. It validates the proof of payment, settles the on-chain transaction, and tells the resource server to release the result. Coinbase Developer Platform (CDP) ships the canonical facilitator on Base; anyone can run an alternative facilitator that supports more chains, more assets, more KYC profiles, or more settlement currencies. For European merchants, the most useful "more" is EUR settlement : the agent pays USDC, the merchant gets EUR in their IBAN, the whole thing happens in one HTTP exchange. ## Why a US-native facilitator is not enough for EU merchants If you are a European merchant accepting agent payments through Coinbase CDP, you receive USDC in a Coinbase Wallet on Base. To get EUR in your bank account, you have to: open a Coinbase exchange account (or a CASP partner account elsewhere), transfer USDC there, sell USDC for EUR, withdraw EUR via SEPA. That is four manual steps, two custody handoffs, and 1-3 business days of float. Worse, the regulated entity that converts USDC to EUR is in the US, which makes the EU MiCA regulatory perimeter unclear for sustained business volume. An EU-native facilitator collapses those four steps into one HTTP round-trip and keeps the regulated perimeter inside the EU. The MiCA, AMLR and Travel Rule obligations attach to a European CASP partner that has already obtained the necessary authorisations. The merchant only has to be onboarded once via Sumsub KYB. ## Six selection criteria - Native EUR settlement via SEPA Instant in under 15 seconds. Not a separate off-ramp API. Not "we'll wire you EUR in T+1." Inside the same HTTP 402 round-trip, end-to-end. - MiCA-aligned partner routing with named CASP partners. The facilitator should publicly name the licensed entity that holds your USDC and converts it to EUR. If they won't name the partner, walk away. - KYA trust scoring on the agent wallet before settlement. Sanctions screening, ERC-8004 identity check, behavioural risk signals. Without this you ship without an agent-side risk filter, and you are exposed when a bad agent finds your endpoint. - Multi-chain ingress. Agents will pay from whichever chain holds their USDC float β€” Base today, Polygon and Arbitrum tomorrow, Solana the day after. A single-chain facilitator forces agents to bridge first, which costs gas and time. - Both x402 and MPP protocol support on every paid endpoint. The Machine Payments Protocol (Stripe / Tempo) is the other leading 402-payments standard. A facilitator that supports both on the same response future-proofs your endpoint. - Self-serve KYB onboarding via Sumsub or equivalent in under 30 minutes. If onboarding takes a sales call, you are not a real platform. Self-serve KYB with documented Sumsub integration is the bar. ## How the current options score | | Criterion | Coinbase CDP | US-focused stablecoin orchestration | AsterPay | EUR settlement <15s | No (USDC out) | USD focus | Yes | Regulatory coverage | US-licensed | US-licensed | EU-native via licensed European payment partners (disclosed to onboarded customers under NDA) | KYA trust scoring | No | No | Yes (0-100, ERC-8004) | Multi-chain | Base only | Multiple | Base, Polygon, Arbitrum, Optimism, Ethereum, Solana | x402 + MPP both | x402 only | MPP via Tempo | Both on every endpoint | Self-serve KYB <30min | Yes | Yes | Yes (Sumsub) Read across the table: if you are a European merchant accepting agent payments and you want EUR in your bank account, AsterPay is currently the only option that scores yes on all six. The other two categories are excellent products for different problems β€” CDP is the right choice if you want USDC and you are comfortable with US-licensed custody; US-focused stablecoin orchestration platforms are the right choice if your customers and bank accounts are USD-denominated. ## The EU-native category is small but not for long Europe has roughly 30 million SMEs. Agent commerce is just starting to reach them. The category of "EU-native x402 facilitator with EUR settlement" has one production entrant today (AsterPay) and we expect at least three more by end of 2026 as Coinbase CDP, Stripe and possibly a Linux Foundation reference implementation expand. The selection criteria above will still apply β€” the differentiation will move to which facilitator has the most EU CASP partners on the back end and the most distribution into EU-resident agent runtimes (Cursor, Claude, ChatGPT, Mistral) on the front. ### Related guides - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - [EUR settlement for AI agents β€” buyer's guide](/learn/eur-settlement-for-ai-agents/) - [MiCA-aligned stablecoin settlement](/learn/mica-aligned-stablecoin-settlement/) - [AsterPay vs Coinbase CDP](/compare/asterpay-vs-coinbase-cdp/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay is not affiliated with Aster (ASTER) DEX, the BNB Chain perpetual exchange, and has no native token. --- # ERC-8004 explained β€” On-chain agent identity standard | AsterPay Source: Markdown mirror: > ERC-8004 is the Ethereum standard for on-chain AI agent identity. Registry contract, agent IDs, attestations and how AsterPay uses ERC-8004 to anchor KYA trust scoring on Base. [← Learn](/learn/) # ERC-8004 explained β€” on-chain agent identity By Petteri , Co-founder of AsterPay Β· Last updated 23 April 2026 Β· 4 min read Answer ERC-8004 is the Ethereum standard for on-chain AI agent identity. It defines a registry contract that issues a unique numeric Agent ID to any agent that registers, binds the ID to one or more wallet addresses, and lets third parties attach signed attestations (compliance, reputation, capability claims) to the ID. The canonical Base deployment lives at `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`. ## Why does an AI agent need on-chain identity? Off-chain identity systems assume a stable URL or a corporate registrar β€” neither holds up for autonomous agents. Agents move between operators, get cloned, get retired, get re-keyed. A domain expires; a startup pivots; a wallet gets compromised and rotated. ERC-8004 anchors a long-lived identity to a numeric ID that survives all of those events. Reputation accumulates across the agent's lifetime, attached to the ID rather than to any single key, domain or company. ## What does the standard actually define? - Registry contract β€” singleton per chain. `register(metadataURI)` mints an Agent ID. `updateMetadata(id, newURI)` rotates the off-chain document. - Agent ID β€” monotonically increasing uint256. AsterPay is ID 16850 on Base. - Address binding β€” one or more EVM addresses can be bound to an Agent ID via signed messages. This is how reputation survives key rotation. - Attestations β€” third parties can attach EAS-style signed claims to an Agent ID: "this agent has KYB", "this agent passed sanctions screening", "this agent has a posted bond of X USDC". Attestations are public, verifiable and revocable. - Metadata URI β€” the off-chain document, conventionally an `agent.json` hosted at `/.well-known/agent.json`. Includes capabilities, supported chains, payment endpoints. ## How does ERC-8004 relate to KYA? ERC-8004 is the identity layer; [KYA](/learn/what-is-kya/) is the trust-scoring layer. KYA uses ERC-8004 registration as one of its seven components (worth 15 points). An agent without ERC-8004 caps out at 85 KYA points β€” enough for production use, but the enterprise tier (80-100) effectively requires on-chain identity. AsterPay also publishes its own ERC-8004 attestations to vouch for KYB-completed operators, so any third-party facilitator can use AsterPay's attestation as evidence in their own scoring. ## How is AsterPay registered? AsterPay's ERC-8004 registration on Base: ``` { "agentId": 16850, "registry": "0x8004A169FB4a3325136EB29fA0ceB6D2e539a432", "chain": "base", "boundAddresses": ["0xd5f8481D8F25d3966d2010DBf9B47fFbdf745A9E"], "metadataURI": "https://asterpay.io/.well-known/agent.json", "operator": "AELIRA LTD" } ``` The same record is exposed in our [/.well-known/agent.json](/.well-known/agent.json) under the `identity.erc8004` field, so any compliant agent or facilitator can verify the binding without an RPC call. ## How do I register my own agent? Three options, in order of effort: - MCP tool β€” `npm install @asterpay/mcp-server`. The `register_erc8004_agent` tool handles metadata upload, contract call and verification. ~30 seconds. - CLI β€” `npx @asterpay/erc8004 register --metadata ./agent.json --rpc `. - Direct contract call β€” call `register(string metadataURI)` on the registry contract from any wallet. Gas is ~0.001 ETH on Base. After registration, plug the returned Agent ID into your `agent.json` under `identity.erc8004.agentId` and AsterPay's KYA endpoint will start picking it up within a few minutes. ### Related - β†’ [What is KYA?](/learn/what-is-kya/) - β†’ [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - β†’ [AsterPay agent.json](/.well-known/agent.json) - β†’ [ERC-8004 EIP](https://eips.ethereum.org/EIPS/eip-8004) --- # EUR settlement for AI agents β€” buyer's guide for European merchants | AsterPay Source: Markdown mirror: > Buyer [← Learn](/learn/) # EUR settlement for AI agents β€” buyer's guide By Petteri , Co-founder of AsterPay Β· Last updated 23 April 2026 Β· 6 min read Answer EUR settlement for AI agent commerce means the merchant receives euros in their bank account when an AI agent pays in stablecoin. The agent pays in USDC, EURC or EURCV; the rail converts to EUR via a regulated CASP partner; SEPA Instant pushes the EUR to the merchant's IBAN. As an EU merchant choosing a vendor, evaluate on six criteria: MiCA-aligned partner routing, SEPA Instant native, sub-15-second latency, transparent pricing, self-serve KYB and native x402 facilitator support. ## Why this matters now In 2026 AI agents have moved from chat companions to autonomous purchasing agents β€” booking calls, buying APIs, paying for compute, ordering subscriptions. For a European merchant the question is no longer "should we accept agent payments?" but "which rail?" Most existing payment vendors were designed for human checkout. Card processors balk at machine-initiated transactions. Crypto-only rails leave the merchant with an accounting mess. EUR settlement is the operational layer that lets you accept the new wave without disrupting your finance team. Your invoice still shows EUR. Your VAT return still works. Your bank reconciliation still maps one-to-one with the API calls you billed for. ## Six decision criteria ### 1. MiCA-aligned partner routing The Markets in Crypto-Assets Regulation has been in full force since December 2024. Any vendor swapping stablecoins for EUR on your behalf must either be authorised as a Crypto-Asset Service Provider (CASP) themselves, or route through a licensed CASP partner. Ask for a written attestation of which CASP entity holds and converts the funds. AsterPay routes through four licensed CASP partners and operates as a technical service provider behind those authorisations. ### 2. SEPA Instant β€” not regular SEPA Regular SEPA credit transfers settle in 1-2 business days. SEPA Instant settles in under 10 seconds, 24/7/365 β€” including weekends and bank holidays. Since the Instant Payments Regulation, every euro-area bank is required to offer SEPA Instant at parity pricing. Insist on it. A vendor that only supports regular SEPA is two decades out of date for agent commerce. ### 3. End-to-end latency under 15 seconds From the agent's HTTP 402 to the EUR landing in your bank, the entire flow should complete in under 15 seconds (P95). Anything longer means the agent times out before getting the API response, and the merchant is stuck with orphaned payments. AsterPay's production median is 7 seconds; P95 is 10 seconds. ### 4. Transparent pricing Demand a single bps number on the EUR settlement amount, plus a transparent CASP spread surfaced in the `/v1/settlement/estimate` response. Watch for hidden FX markups (a separate "spread" of 1-2% applied to the conversion rate, common with legacy off-rampers) and per-transaction KYC fees. AsterPay's published pricing is 50 bps + CASP spread (30-80 bps); total all-in is typically 80-130 bps. ### 5. Self-serve KYB onboarding If onboarding requires a sales call, you are looking at the wrong vendor for agent commerce. Self-serve KYB through Sumsub or Veriff in under 30 minutes is the production standard. Once KYB is done, payouts run automatically with no per-transaction KYC. ### 6. Native x402 facilitator support This is the test that eliminates most candidates. Many EU off-ramp providers and US-focused stablecoin orchestration platforms have great fiat rails but cannot verify x402 payment proofs end-to-end. They expose a separate API for "USDC in, EUR out" but you have to wire the x402 verification yourself. A native x402 facilitator does both in one call. ## Vendor comparison | | | AsterPay | BVNK | Generic stablecoin offramp API | EU regulatory coverage | Yes (via licensed European payment partners) | EMI | Varies | SEPA Instant | Yes | Yes | Varies | x402 facilitator native | Yes | No | No | KYA trust scoring | Yes | No | No | Self-serve KYB | ~10 min | Sales-led | Sales-led | Pricing transparent | Yes β€” 50 bps + partner spread | Custom | Custom | P95 latency | ~10 sec | Minutes | Hours Full methodology and side-by-side details at [/compare](/compare/). ### Quick procurement checklist - MiCA-aligned partner CASP routing β€” written attestation - SEPA Instant native, not regular SEPA - End-to-end latency < 15 sec (P95) - Flat bps pricing, no hidden FX markup - Self-serve KYB via Sumsub or Veriff in < 30 min - Native x402 facilitator (verifies payment proofs end-to-end) - Status page + incident webhook for operational alerts - KYA trust scoring for inbound agent screening ## How to evaluate AsterPay specifically - Run a free settlement estimate with no signup: `curl https://x402.asterpay.io/v1/settlement/estimate?amount=1000`. - Read the [x402 capability manifest](/.well-known/x402.json) β€” every supported endpoint, asset and chain is enumerated. - Check the live [status page](https://api.asterpay.io/v1/incidents/status) β€” uptime visible end-to-end across all settlement and payment partners. - Read the [MiCA-aligned stablecoin settlement guide](/learn/mica-aligned-stablecoin-settlement/) for the regulatory roadmap and CASP partner list. - Email [samantha@asterpay.io](mailto:samantha@asterpay.io) for KYB onboarding β€” typically online in 24 hours. ### Related - β†’ [What is x402 EUR settlement? (pillar guide)](/learn/what-is-x402-eur-settlement/) - β†’ [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - β†’ [Side-by-side vendor comparison](/compare/) - β†’ [MiCA-aligned stablecoin settlement guide](/learn/mica-aligned-stablecoin-settlement/) --- # How do AI agents pay merchants? β€” The 2026 guide to agent checkout and EUR settlement | AsterPay Source: Markdown mirror: > How AI agents pay merchants in 2026: ACP, UCP, AP2, Visa TAP, x402 and MPP explained. How the checkout works, and how a European merchant actually gets paid in EUR. [← Learn](/learn/) # How do AI agents pay merchants? The 2026 guide to agent checkout and EUR settlement By Petteri , Co-founder of AsterPay Β· Published: 13 June 2026 Β· Last updated: 13 June 2026 Β· 11 min read Answer AI agents pay merchants through one of two models. In delegated-card checkout β€” ACP (OpenAI + Stripe), UCP and AP2 (Google), Visa Trusted Agent Protocol β€” the agent presents a scoped, single-use payment token or a signed mandate, and the merchant charges it through its existing card processor. In native crypto payment β€” x402 (Coinbase) and MPP (Stripe / Tempo) β€” the agent pays in stablecoins over HTTP and a facilitator settles it on-chain. In both models the merchant stays the merchant of record. For a European merchant the open question is the last leg: how the payment becomes EUR in a bank account. That is what AsterPay settles, via SEPA Instant in under 10 seconds. ## The two ways an AI agent can pay Every agent-payment standard shipping in 2026 falls into one of two families. Getting this split clear is the whole game, because the press treats them as competitors when they actually solve different layers. - Delegated-card checkout β€” the agent never sees the card number. A payment provider issues a scoped, single-use token (or the user signs a cryptographic mandate), and the merchant charges it like any other card transaction. This is the model behind OpenAI and Stripe's Agentic Commerce Protocol, Google's Universal Commerce Protocol and Agent Payments Protocol, and Visa's Trusted Agent Protocol. - Native crypto payment β€” the agent pays in stablecoins directly over HTTP, with no card network in the loop. This is the model behind Coinbase's x402 and the Stripe/Tempo Machine Payments Protocol (MPP). A facilitator verifies the payment and settles it on-chain. Cards suit consumer e-commerce and high-value, mandate-bound purchases like travel and procurement. Stablecoins suit API access, digital goods, compute and cross-border micropayments, where card fees and multi-day settlement do not work. Larger merchants are wiring up both. ## What are ACP, UCP, AP2, Visa TAP, x402 and MPP? Here is the full 2026 landscape on one screen, with who built each standard and what layer it owns. | | Standard | Built by | Layer it owns | How the agent pays | ACP (Agentic Commerce Protocol) | OpenAI + Stripe | Checkout inside AI apps (ChatGPT Instant Checkout) | Delegated card token (Shared Payment Token) | UCP (Universal Commerce Protocol) | Google, Shopify, Nexi, 20+ partners | Full commerce lifecycle, discovery to order | Multiple handlers (Google Pay, Shop Pay, AP2) | AP2 (Agent Payments Protocol) | Google + 60+ partners | Payment authorization (mandates) | Signed Intent / Cart / Payment Mandates | Visa TAP (Trusted Agent Protocol) | Visa | Agent identity at card acceptance | Authenticated agent + card credential | x402 | Coinbase | Crypto settlement over HTTP 402 | Stablecoins (USDC) on-chain | MPP (Machine Payments Protocol) | Stripe / Tempo | Metered machine payments | Stablecoins / fiat rails Sources: [Stripe ACP announcement](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce), [Agentic Commerce Protocol docs](https://www.agenticcommerce.dev/docs/getting-started/sellers). See also our [x402 vs MPP comparison](/learn/x402-vs-mpp/). ## How does an AI agent check out and pay a merchant, step by step? The mechanics are remarkably consistent across standards. An agent does not click through your checkout UI β€” it calls your API. The canonical sequence: - Discovery β€” the merchant exposes machine-readable product, price and policy data (Product, Offer and FAQ schema) and a manifest, e.g. at `/.well-known/ucp`, so the agent can find and parse the catalog without scraping. - Checkout session β€” the agent calls `create_checkout`, builds a cart, and the merchant returns line items, taxes, shipping and declared payment capabilities. - Authorization β€” the user (present) or the user's pre-authorized agent (absent) signs a mandate or receives a delegated, single-use payment token scoped to a maximum amount. In AP2 this is the dual-signed Cart Mandate: the merchant signs the price, the user signs the purchase. - Payment β€” the agent submits the token or the stablecoin payment to the merchant. The agent never holds the user's raw card credentials. - Accept or decline + settle β€” the merchant validates the authorization, uses fraud and trust signals to accept or decline, charges through its payment provider (or has a facilitator settle the stablecoin), and creates the order. For the crypto path, the same five steps collapse into a single HTTP retry. The agent calls the endpoint, gets an HTTP 402 with payment requirements, signs a stablecoin payment, retries with the proof, and a facilitator settles it. We break that down in [What is x402?](/learn/what-is-x402/) ## Is the merchant still the merchant of record? Yes β€” and this is the single most reassuring fact for a business worried about agents. Across ACP, UCP, AP2 and x402, the merchant remains the merchant of record . As OpenAI and Stripe put it in the ACP spec, the business "receives a checkout request and secure payment credential details from the AI agent" and "can choose to accept or decline the transaction using payment and fraud signals, and is the merchant of record." The merchant calculates prices, manages inventory, processes the payment through its own provider, and owns the post-purchase relationship. The agent and the platform sit in front of checkout; they do not become the seller. ## How does a European merchant actually get paid in EUR? This is the question the card-centric standards leave open, and it is where most "agentic commerce" coverage stops. Authorizing a payment is not the same as settling it into spendable euros. Compare the last leg across rails: | | Rail | What the merchant receives | Settlement time | EUR-in-bank? | ACP / Visa TAP | Card funds via existing acquirer | 1-7 days | Yes, but via card rails & card fees | Raw x402 (Coinbase CDP) | USDC on Base | ~2-4 sec on-chain | No β€” merchant must off-ramp USDC themselves | MPP (raw) | Stablecoin or fiat, processor-dependent | Varies | Depends on processor | x402 / MPP via AsterPay | EUR on the merchant's IBAN | <10 sec SEPA Instant | Yes β€” merchant never touches crypto The card rails get a European merchant euros eventually, but on card economics: roughly 1.4-2.9% in fees plus FX markup and multi-day settlement. The crypto rails are instant and near-free at the protocol layer, but raw x402 leaves a USDC balance on Base that the merchant still has to convert, value for VAT, and reconcile. Neither solves the actual European requirement: EUR in a bank account, with a clean reference, ready for accounting . ## What the card standards leave unsolved for EU merchants The ACP/UCP/card-network stack was designed in the US around card-based methods. Mollie, building agentic checkout for Europe, put the gap plainly: the current protocol standards are "initially US-centric and support only global, card-based methods (Apple Pay, Google Pay, Cards)" and this "is incomplete for European" commerce. Four things stay open for a European seller: - EUR settlement β€” converting the payment to euros on a European bank rail (SEPA Instant), not a card timeline. - MiCA alignment β€” when stablecoins are involved, the off-ramp is a regulated activity that must run through a licensed Crypto-Asset Service Provider. - Agent identity and trust (KYA) β€” knowing which agent is paying, on whose authority, and within what limits. See [Know Your Agent (KYA) compliance in Europe](/learn/know-your-agent-compliance-eu/). - Payee verification β€” resolving and validating the merchant's IBAN, including PSD2 Verification of Payee. See the [Merchant Payment Endpoint](/learn/merchant-payment-endpoint/). AsterPay is built to close exactly these four gaps as a layer that sits underneath whichever checkout protocol the agent speaks. It is complementary to ACP and UCP, not a competitor to them. ## Which rail should a merchant support? Pick by what you sell, not by hype. A practical decision guide: | | You sell… | Primary rail | Why | Consumer goods (ChatGPT / Gemini shoppers) | ACP or UCP | Where the agent traffic and the checkout UX live | APIs, data, compute, digital goods | x402 or MPP | Per-call micropayments, no card minimums, instant | High-value / B2B procurement | AP2-on-cards or MPP | Mandate-bound authorization, audit trail | Anything, and you are in the EU and want EUR | x402 / MPP via AsterPay | EUR to IBAN in <10s, MiCA-aligned, KYA built in ## How a merchant becomes payable by agents in EUR For the EUR-settlement leg specifically, the integration is short: ``` // Add x402 / MPP middleware to your API or checkout endpoint app.use('/v1/*', x402Middleware({ facilitator: 'https://x402.asterpay.io', price: '0.01', currency: 'USDC' })); // 1. An agent (any x402- or MPP-compatible) calls your endpoint // 2. AsterPay verifies the agent (KYA), screens sanctions in EUR // 4. EUR lands on your IBAN via SEPA Instant in ``` The merchant never holds USDC; the agent never holds EUR. AsterPay is non-custodial β€” funds pass through licensed CASP partners under MiCA, never sitting on AsterPay's balance sheet. KYB onboarding takes about 10 minutes, after which payouts run automatically with no per-transaction KYC. Full mechanics in [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) ### See the EUR a payment would land Get a USDC β†’ EUR settlement estimate for any amount β€” no signup, no card, no crypto wallet required. [Get a $100 β†’ EUR estimate β†’](https://x402.asterpay.io/v1/settlement/estimate?amount=100) PL Petteri Co-founder of AsterPay (AELIRA LTD). Building the EU-native x402 / MPP facilitator and EUR settlement layer for AI agent commerce. [@Asterpayment](https://x.com/Asterpayment) ## Related reading - [What is x402 EUR settlement? β€” the definitive guide](/learn/what-is-x402-eur-settlement/) - [x402 vs MPP β€” which agent payment protocol should you support?](/learn/x402-vs-mpp/) - [How do AI agents pay any business? The Merchant Payment Endpoint (MPE)](/learn/merchant-payment-endpoint/) - [Know Your Agent (KYA) compliance in Europe](/learn/know-your-agent-compliance-eu/) - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - [How AsterPay compares β€” Stripe, Wise, BVNK, raw x402](/compare/) ### References - Stripe. "Developing an open standard for agentic commerce" (2026). [stripe.com](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) - Agentic Commerce Protocol. "Sellers β€” getting started" (2026). [agenticcommerce.dev](https://www.agenticcommerce.dev/docs/getting-started/sellers) - OpenAI. "Delegated Payment Spec β€” Agentic Commerce" (2026). [developers.openai.com](https://developers.openai.com/commerce/specs/payment) - Google. "AP2 β€” Agent Payments Protocol" mandates as verifiable credentials (2026). - Mollie. "Agentic commerce and European payments β€” FAQ" (2026). [mollie.com](https://www.mollie.com/growth/agentic-commerce-european-payments-faq) - Coinbase. "x402 Protocol Specification" (2025). [github.com/coinbase/x402](https://github.com/coinbase/x402) - European Commission. "Instant Payments Regulation", Regulation (EU) 2024/886, in force 9 January 2025. Have a correction or want this page to cover a different angle? Email [samantha@asterpay.io](mailto:samantha@asterpay.io). We update this page every quarter. --- # How to convert agent stablecoin payments to EUR β€” step by step | AsterPay Source: Markdown mirror: > Step-by-step guide: how to convert AI agent USDC payments to EUR in your bank account. SEPA Instant, MiCA-aligned partner routing, KYB onboarding, code examples. [← Learn hub](/learn/) # How to convert agent stablecoin payments to EUR β€” step by step Updated 3 May 2026 Β· 7 minute read Β· By Petteri, Co-founder Short answer Sign up, complete KYB, return HTTP 402 from your endpoint pointing to AsterPay as the facilitator with your IBAN as the EUR settlement target. The agent pays USDC, AsterPay swaps to EUR via a licensed CASP partner, and SEPA Instant delivers EUR to your bank account in under 15 seconds. You never hold USDC. Total cost typically 80-130 bps. ## Six steps from zero to EUR-in-bank 1 ### Sign up and complete KYB Create a merchant account at [app.asterpay.io/signup](https://app.asterpay.io/signup). Sumsub KYB takes 30 minutes for a typical EU-incorporated entity. You provide entity name, registration number, beneficial owners and the IBAN where EUR settlements should land. 2 ### Get an API key From the dashboard generate an API key. Store as `ASTERPAY_API_KEY` in your backend environment. Never expose it to a frontend or an agent prompt. 3 ### Add x402 to your endpoint One line of middleware. AsterPay ships drop-in middleware for Express, Fastify, FastAPI and Next.js. Example for Express: ``` import { asterpay } from '@asterpay/x402-express'; app.get('/api/forecast', asterpay({ priceEur: 0.05, settlementIban: process.env.MY_IBAN }), (req, res) => res.json({ forecast: '...' }) ); ``` 4 ### Agent pays The agent receives the 402, signs an EIP-3009 `transferWithAuthorization` for USDC on its preferred chain (Base, Polygon, Arbitrum, Optimism, Ethereum or Solana), and resends the request with the `X-PAYMENT` header. Any x402-aware agent SDK does this automatically β€” `x402-fetch`, the AsterPay MCP server, the Coinbase x402 client. No agent-side configuration needed. 5 ### AsterPay settles AsterPay verifies the payment proof, runs KYA trust scoring on the agent wallet, executes the on-chain settlement, swaps USDC to EUR through a licensed European payment partner (auto-routed by amount, currency and partner availability), and pushes EUR to your IBAN via SEPA Instant. End-to-end under 15 seconds in normal conditions. Specific partner identities are disclosed to onboarded customers under partnership-only disclosure terms. 6 ### Reconcile in EUR Each settlement returns a `Payment-Receipt` header with the on-chain tx hash, the SEPA reference, the EUR amount net of fees, and the FX rate at moment of swap. Feed it into your accounting software for clean EUR-denominated journal entries. No FX drift, no double bookkeeping, no monthly stablecoin reconciliation spreadsheet. ## What the merchant never has to do - Open a crypto exchange account - Hold a USDC balance - Sign up for a separate off-ramp service - Manually trigger a SEPA Instant payout - Reconcile USDC balances against EUR ledger entries at month-end - Choose which chain to receive payments on (multi-chain ingress is automatic) ## What this looks like over a month of agent traffic Sample EU SaaS with 3,000 agent calls per day at EUR 0.05 each: roughly EUR 4,500 monthly settlement. With AsterPay all 4,500 EUR lands in the merchant's IBAN as 90,000 individual SEPA Instant credits aggregated into a single daily payout (configurable). Total fees at 100 bps all-in: EUR 45/month. Compare to Stripe card processing at the same volume: EUR 4,500 Γ— 1.4% + 25c per transaction = EUR 63 + EUR 22.50 = EUR 85.50/month, plus the chargeback risk that does not exist for x402 payments. ## What happens if you serve agents from outside the EU The same flow works for SEPA-area merchants (36 countries including the UK, Norway, Switzerland and Liechtenstein). For US merchants, USD via ACH is on the roadmap; for UK merchants, GBP via Faster Payments is on the roadmap. Outside SEPA, AsterPay can still settle USDC to USDC at your wallet address β€” you skip the EUR conversion but keep the KYA trust filter, the multi-chain ingress and the dual x402+MPP support. ### Related guides - [EUR settlement for AI agents β€” buyer's guide](/learn/eur-settlement-for-ai-agents/) - [Best x402 facilitator in Europe](/learn/best-x402-facilitator-europe/) - [MiCA-aligned stablecoin settlement](/learn/mica-aligned-stablecoin-settlement/) - [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - [Get started in 60 seconds (developer quickstart)](/docs/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay is not affiliated with Aster (ASTER) DEX, the BNB Chain perpetual exchange, and has no native token. --- # Learn β€” x402, EUR settlement, KYA & ERC-8004 explained | AsterPay Source: Markdown mirror: > Definitive entity-first explainers on x402, EUR settlement for AI agents, KYA trust scoring, ERC-8004 agent identity and the regulatory landscape under MiCA. Built for AI agents and the humans who deploy them. [← AsterPay home](/) # Learn β€” x402, EUR settlement & agent payments Entity-first explainers built to be cited by Claude, ChatGPT and Perplexity. Every page is one question, answered in plain English, with sources, dates and a named author. [Pillar guide Β· 9 min ## What is x402 EUR settlement? A definitive guide for AI agent payments How AI agents pay in USDC and merchants receive EUR via SEPA Instant β€” facilitators, regulation under MiCA, costs, and integration. The single most cited document on the topic.](/learn/what-is-x402-eur-settlement/) [Integration Β· eve ## x402 EUR settlement for Vercel eve agents A drop-in eve template: pay x402 services in USDC, settle counterparties in EUR via SEPA Instant, and KYA-check before paying. The money layer for eve agents.](/eve/) [Reference Β· FAQ ## AsterPay FAQ What AsterPay is, supported chains and stablecoins, how the MCP server works, x402, KYA and EUR settlement β€” answered for search engines and AI assistants.](/faq/) [Pillar guide Β· 11 min ## How do AI agents pay merchants? The 2026 map of agent checkout β€” ACP, UCP, AP2, Mastercard Agent Pay, Visa TAP, x402 and MPP β€” and how a European merchant actually gets paid in EUR.](/learn/how-ai-agents-pay-merchants/) [Pillar guide Β· 10 min ## Know Your Agent (KYA) compliance in Europe How the EU AI Act (2 Aug 2026), PSD3, DORA and the MiCA Travel Rule drive agent identity, authorization chains and audit trails β€” and how to implement KYA.](/learn/know-your-agent-compliance-eu/) [Pillar guide Β· 9 min ## The MiCA 1 July 2026 deadline The transitional period ends 1 July 2026 β€” ~200 of 1,200+ firms authorized. What it means for crypto APIs, agent payments and stablecoin-to-EUR settlement.](/learn/mica-deadline-2026-agent-payments/) [Glossary Β· 4 min ## What is x402? The HTTP 402 protocol revival for autonomous AI-agent payments. Origin, mechanics, status in 2026.](/learn/what-is-x402/) [Glossary Β· 4 min ## What is an x402 facilitator? The party that verifies and settles x402 payments. Coinbase CDP, AsterPay, and the rest of the landscape.](/learn/what-is-an-x402-facilitator/) [Comparison Β· 5 min ## x402 facilitator fees compared (2026) Facilitation is free everywhere now. The real fees sit in fiat settlement, screening and compliance β€” the full table.](/learn/x402-facilitator-fees-compared/) [Glossary Β· 5 min ## What is KYA (Know Your Agent)? The agent-payments equivalent of KYC. AsterPay's open trust-scoring framework, schema and tier system.](/learn/what-is-kya/) [Glossary Β· 4 min ## ERC-8004 explained On-chain identity standard for AI agents on Ethereum. Why it matters for trust, payments and reputation.](/learn/erc-8004-explained/) [Buyer's guide Β· 6 min ## EUR settlement for AI agents Buyer's guide for European merchants choosing a stablecoin-to-EUR rail. Decision criteria, MiCA, latency.](/learn/eur-settlement-for-ai-agents/) [Buyer's guide Β· 6 min ## MiCA-aligned stablecoin settlement What MiCA Article 60 requires for stablecoin-to-EUR conversion, the technical-service-provider model, five questions to ask any settlement vendor.](/learn/mica-aligned-stablecoin-settlement/) [Buyer's guide Β· 5 min ## Best x402 facilitator in Europe Why an EU-native facilitator matters, six selection criteria, and a vendor comparison for European merchants.](/learn/best-x402-facilitator-europe/) [How-to Β· 7 min ## How to convert agent stablecoin payments to EUR Step-by-step from KYB to EUR-in-bank. Drop-in middleware, FX-rate locking, settlement reconciliation, and what the merchant never has to do.](/learn/how-to-convert-agent-stablecoin-payments-to-eur/) [Position Β· 7 min ## AsterPay as a MiCA-aligned arbiter for Circle's Refund Protocol Circle's Refund Protocol gives stablecoin payments their missing chargeback primitive but leaves the arbiter slot open. Our position on filling it for European agent commerce, with KYA-graded lockups and EUR-denominated refund coverage.](/learn/asterpay-arbiter-circle-refund-protocol/) [Comparison Β· 5 min ## x402 vs MPP β€” which agent payment protocol should you support? x402 (Coinbase) settles in USDC on-chain; MPP (Stripe/Tempo) settles over fiat rails. Side-by-side comparison β€” and why dual-protocol APIs win.](/learn/x402-vs-mpp/) [Explainer Β· 4 min ## How do AI agents pay any business? The MPE explained The agent knows the company name β€” not the IBAN. The Merchant Payment Endpoint resolves any business to validated payment details with a disclosed verification method, then settles via SEPA Instant.](/learn/merchant-payment-endpoint/) [Use case Β· SaaS ## AI agent payments for SaaS & APIs Make any endpoint agent-payable: agents pay per call in USDC over x402/MPP, and you receive EUR in your bank via SEPA Instant.](/for-saas/) [Use case Β· Marketplaces ## AI agent payments for marketplaces Agents buy across your marketplace, KYA scores every payer, and EUR settles to each seller's IBAN via SEPA Instant.](/for-marketplaces/) Last updated: 13 June 2026 Β· [Read llms-full.txt](/llms-full.txt) for the full machine-readable index Β· [Compare AsterPay vs Stripe / Wise / BVNK / raw x402](/compare/) --- # Know Your Agent (KYA) compliance in Europe β€” EU AI Act, PSD3 & agent-payment liability | AsterPay Source: Markdown mirror: > Know Your Agent (KYA) compliance for the EU: how the EU AI Act (2 Aug 2026), PSD3, DORA and MiCA Travel Rule drive agent identity, authorization chains and audit trails for AI agent payments β€” and how to implement KYA. [← Learn](/learn/) # Know Your Agent (KYA) compliance in Europe: EU AI Act, PSD3 and agent-payment liability By Petteri , Co-founder of AsterPay Β· Published: 13 June 2026 Β· Last updated: 13 June 2026 Β· 10 min read Answer Know Your Agent (KYA) is an identity and authorization framework for AI agents that transact autonomously. Before a payment completes, KYA verifies the agent's identity, the delegation chain from the human or organization that deployed it, the capability boundaries it may operate within, and produces a tamper-resistant audit trail. KYA is not yet a single codified law, but its components are already required in Europe by the EU AI Act (high-risk obligations take full effect 2 August 2026 ), PSD2/PSD3, DORA and the MiCA Travel Rule. KYA is to autonomous agents what KYC is to humans and KYB is to businesses. ## What is Know Your Agent (KYA)? Know Your Agent (KYA) is a four-part verification that a payment system runs before authorizing an agent-initiated transaction: identity , delegation chain , capability boundaries and audit trail . It extends the familiar Know Your Customer (KYC) and Know Your Business (KYB) regimes to a new class of actor β€” autonomous software that can open new wallets at zero cost, act without a human in the loop, and scale activity horizontally faster than any human attacker. The core shift is the question being asked. KYC asks "who is this person?" KYA asks " what is the operational reputation and authority of this agent? " β€” is it sanctions-clean, does it have a verifiable identity, did a real principal authorize it, and is it staying inside the limits it was granted. ## Why does KYA matter now? The 2 August 2026 deadline The forcing function is regulatory. The EU AI Act 's obligations for high-risk AI systems take full effect on 2 August 2026 . The law mandates human oversight for high-risk systems, which in payments effectively requires a human-binding approach to agent authority β€” exactly what a delegation chain provides. At the same time, US standards bodies are moving: NIST's AI Agent Standards Initiative published a concept paper on agent identity and authorization in March 2026, proposing to adapt OAuth, OpenID Connect and SPIFFE for agents. The legal analysis is converging on two structural requirements. As Taylor Wessing's February 2026 review of agentic AI in payments noted, regulators will assess liability when agent payments go wrong using authorization chains and transaction logs . Without a KYA record β€” identity, authorization chain, capability limits β€” liability defaults to the deploying organization. Building KYA-compliant infrastructure now is materially cheaper than retrofitting it under a deadline. ## What is the difference between KYC, KYB and KYA? | | Dimension | KYC (customer) | KYB (business) | KYA (agent) | Subject | A human person | A legal entity | An autonomous AI agent | Core question | Who is this person? | Is this business real and beneficially owned by whom? | Who deployed this agent, and what is it authorized to do? | Permissions | Account-level | Account-level | Task-level: spending caps, categories, time limits | Driving regulation | AML/CFT, national financial law | AML/CFT, beneficial-ownership rules | EU AI Act, PSD3, DORA, NIST agent standards (emerging) | Identity lifetime | Long-lived | Long-lived | Can be ephemeral β€” new wallet at zero cost ## Which EU regulations drive KYA? No single rule says "do KYA," but four regimes each require a piece of it. Together they make KYA the practical way to comply. - EU AI Act β€” high-risk obligations from 2 August 2026. Article 12 requires automatic, tamper-resistant logging over the system lifecycle; Article 14 requires human oversight; Article 50 sets transparency duties. Annex III classifies AI used in creditworthiness, fraud detection, AML risk profiling and automated financial decisioning as high-risk. ([artificialintelligenceact.eu](https://artificialintelligenceact.eu/)) - PSD2 β†’ PSD3 β€” PSD2 Strong Customer Authentication assumes a human authorizes each payment; it does not mention AI. PSD3 is expected to start formalizing delegated payment initiation by agents and Strong Customer Authentication for autonomous actors. Until then, fiat-side agent payments still need a human authorization anchor β€” which a delegation chain records. - DORA β€” the Digital Operational Resilience Act requires financial entities to manage third-party (including AI) operational risk, which means knowing and governing the agents in your flows. - MiCA Travel Rule β€” for crypto transfers, originator and beneficiary information must travel with the transaction above threshold. For agent stablecoin payments, that requires identifying the agent and its operator. AsterPay automates the Travel Rule for transfers over EUR 1,000. ## What are the four checks in a KYA verification? A KYA system runs four checks before a payment is authorized. Each maps to a regulatory requirement above. - Identity β€” the agent has a verifiable identity, ideally on-chain (e.g. [ERC-8004](/learn/erc-8004-explained/)) and bound to its operator. This satisfies the "who acted" question. - Delegation chain β€” cryptographic proof that the human or organization authorized this specific agent to act on its behalf, within stated scope. This is the authorization-chain requirement regulators will test. - Capability boundaries β€” declared and enforced limits: spend per transaction, per day, per category; allowed counterparties; prohibited actions. Crucially, these are enforced at the payment layer, not inside agent code , so a compromised or misaligned agent cannot exceed them. - Audit trail β€” a tamper-resistant log of identity, authorization and the decision, sufficient to attribute liability if a payment is later disputed. This is the Article 12 logging requirement. ## Inbound KYA vs internal KYA KYA splits into two deployments, and conflating them is a common mistake. - Inbound KYA β€” governing external customer agents that pay you or act on accounts you hold. You verify the agent before it transacts. This is largely crypto-native or in pilot today, because fiat-side Strong Customer Authentication still expects a human. - Internal KYA β€” governing the AI agents your own organization deploys in fraud, KYC, AML, onboarding and financial decisioning. These are the high-risk systems the EU AI Act regulates directly, so the need here is immediate, not future. AsterPay's KYA is primarily an inbound control: it verifies the paying agent on behalf of the merchant, so the merchant inherits a compliant record without building agent governance themselves. ## How does AsterPay implement KYA? AsterPay runs KYA on every agent payment it facilitates. The model is an open 0-100 trust score across seven components, mapped to five payment tiers with enforced limits: | | KYA component | What it checks | Wallet age | Time since first on-chain activity | Wallet activity | Volume and recency of legitimate transactions | Sanctions screening | OFAC / EU / UN lists via Chainalysis, in <100ms | ERC-8004 identity | On-chain agent identity bound to operator | Operator KYB | The company behind the agent has completed KYB | Transaction history | Settlement, dispute and refund rates over the agent's lifetime | Trust bond | Optional posted USDC bond, slashed on confirmed bad behavior Sanctions screening runs on every transaction, the Travel Rule is automated for transfers over EUR 1,000, and the seven-component breakdown doubles as the explanation required under the EU AI Act's transparency duties. The KYA v1 schema is published openly at [/.well-known/kya-schema-v1.md](/.well-known/kya-schema-v1.md) so other facilitators and merchants can adopt it as a shared trust language β€” the way FICO became a default credit-score language without being owned by a single bank. The full scoring rubric and tier limits are in [What is KYA (Know Your Agent)?](/learn/what-is-kya/) ## How do I check an agent's KYA score? A free, unauthenticated GET request returns the score, tier, component breakdown, sanctions status and recommended limits: ``` curl https://x402.asterpay.io/v1/agent/trust-score/0xYourAgent { "score": 72, "tier": "trusted", "blocked": false, "sanctions": { "clean": true, "provider": "chainalysis" }, "limits": { "maxPerTx": 5000, "maxDaily": 25000 } } ``` ### Check any agent's trust score Run a KYA trust-score lookup on any wallet address β€” free, no signup, no auth. [Open the KYA API docs β†’](https://x402.asterpay.io/docs) PL Petteri Co-founder of AsterPay (AELIRA LTD). Building the EU-native trust and EUR-settlement layer for AI agent commerce, including the open KYA framework. [@Asterpayment](https://x.com/Asterpayment) ## Related reading - [What is KYA (Know Your Agent)? β€” the scoring framework](/learn/what-is-kya/) - [ERC-8004 explained β€” on-chain agent identity](/learn/erc-8004-explained/) - [How do AI agents pay merchants?](/learn/how-ai-agents-pay-merchants/) - [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - [MiCA-aligned stablecoin settlement](/learn/mica-aligned-stablecoin-settlement/) ### References - European Parliament & Council. "Artificial Intelligence Act", Regulation (EU) 2024/1689 β€” high-risk obligations applicable 2 August 2026. [artificialintelligenceact.eu](https://artificialintelligenceact.eu/) - European Commission. "Markets in Crypto-Assets Regulation (MiCA)", Regulation (EU) 2023/1114, incl. Travel Rule under Regulation (EU) 2023/1113. - European Commission. "Digital Operational Resilience Act (DORA)", Regulation (EU) 2022/2554. - European Commission. PSD3 / PSR proposals on payment services (in legislative process, 2025-2027). - Taylor Wessing. "Agentic AI in payments β€” authorization chains and transaction logs" (February 2026). - NIST. "Concept paper on agent identity and authorization", AI Agent Standards Initiative (March 2026). - AsterPay. "KYA Trust Score schema v1" (2026). [asterpay.io/.well-known/kya-schema-v1](https://asterpay.io/.well-known/kya-schema-v1) Have a correction or want this page to cover a different angle? Email [samantha@asterpay.io](mailto:samantha@asterpay.io). We update this page every quarter. --- # How do AI agents pay any business? The Merchant Payment Endpoint (MPE) explained | AsterPay Source: Markdown mirror: > An AI agent knows the company name β€” but not its IBAN. The Merchant Payment Endpoint (MPE) resolves any business name or VAT number to validated payment details with a disclosed verification method, then settles via SEPA Instant. [← Learn](/learn/) # How do AI agents pay any business? The Merchant Payment Endpoint (MPE) explained By Petteri , Co-founder of AsterPay Β· Last updated 9 June 2026 Β· 4 min read Answer An AI agent usually knows who it wants to pay β€” "Acme GmbH", a VAT number, an invoice header β€” but not where to send the money. A Merchant Payment Endpoint (MPE) closes that gap: it resolves a business name or VAT number to validated payment details (IBAN/BIC with full structure and checksum validation, verification method disclosed in every response), and can chain straight into settlement. AsterPay operates an MPE as Layer 2 of its agent commerce stack β€” resolution is free, and `POST /v1/mpe/settle` runs resolve β†’ validate β†’ trust check β†’ SEPA Instant payout in one call. ## The problem nobody built for Agent payment protocols like x402 assume the agent already has a recipient address. Real commerce does not work that way. An agent processing an invoice, restocking inventory, or paying a supplier starts from a business identity : a legal name, a VAT number, a registry entry. Between that identity and a SEPA payment lies the lookup problem β€” and getting it wrong means money sent to the wrong account, which is exactly how invoice fraud drains billions from human accounts-payable teams every year. ## What the MPE does - Resolve β€” `GET /v1/mpe/merchants/resolve?business_id=FI-DEMO-0001&business_id_type=demo` (a public demo merchant) resolves the payee only from provable sources : AsterPay's verified merchant registry, the merchant's signed payment manifest (`/.well-known/pay.json`), or a structured e-invoice (EN16931 UBL/CII). Every resolved IBAN carries a logged provenance and confidence level (`verified` / `document` / `asserted`), so the agent always knows the origin of the account it is about to pay. - Validate β€” the resolved IBAN passes full structure and checksum validation, and every response discloses the verification method used (`vop_method`). Bank-side PSD2 Verification of Payee (VoP) name matching is being added via partner PSPs; the MPE never claims a name match it has not performed. - Settle β€” `POST /v1/mpe/settle` chains the full pipeline: resolve, payee validation, the paying agent's [KYA trust check](/learn/what-is-kya/), then USDCβ†’EUR conversion and SEPA Instant payout. Agent pays stablecoins; the business receives euros, typically in under 10 seconds. ## Where MPE sits in the stack | | Layer | Question it answers | AsterPay surface | Layer 1 β€” KYA trust | "Can I trust this agent?" | Trust score 0–100, sanctions, ERC-8004 identity | Layer 2 β€” MPE | "Where do I send the money?" | Resolve + validated IBAN | Layer 3 β€” Settlement | "How does it become euros?" | USDCβ†’EUR via SEPA Instant ## What it costs Resolution is free . Settlement carries the standard EUR fee: 0.5% + €0.10 per transaction on the EU rail (1.5% + €1.00 on the US rail). No subscription, no token β€” pay per settlement. ## Try it ``` # Resolve a merchant by VAT number (free, no auth) curl "https://x402.asterpay.io/v1/mpe/merchants/resolve?business_id=FI-DEMO-0001&business_id_type=demo" # Full pipeline: resolve β†’ validate β†’ KYA β†’ SEPA Instant curl -X POST "https://x402.asterpay.io/v1/mpe/settle" \ -H "Content-Type: application/json" \ -d '{"business_id":"FI-DEMO-0001","business_id_type":"demo","amount_usdc":250}' ``` ### Related - β†’ [What is KYA? (Layer 1)](/learn/what-is-kya/) - β†’ [What is x402 EUR settlement? (Layer 3)](/learn/what-is-x402-eur-settlement/) - β†’ [x402 vs MPP](/learn/x402-vs-mpp/) - β†’ [Developer docs](/docs/) --- # MiCA-aligned stablecoin settlement β€” what European merchants need to know | AsterPay Source: Markdown mirror: > MiCA-aligned stablecoin-to-EUR settlement explained for European merchants accepting AI agent payments. Article 60 CASP rules, partner routing, what to ask vendors, vendor checklist. [← Learn hub](/learn/) # MiCA-aligned stablecoin settlement β€” what European merchants need to know Updated 3 May 2026 Β· 6 minute read Β· By Petteri, Co-founder Short answer MiCA-aligned means the vendor either holds a CASP authorisation themselves or routes the on-chain to EUR swap through a licensed CASP partner. Either is legal. The technical-service-provider model (AsterPay's choice) lets you ship faster while keeping the regulated perimeter on the partner side. Ask any settlement vendor five specific questions before you sign. ## What MiCA Article 60 actually requires The Markets in Crypto-Assets Regulation entered full force on 30 December 2024. Article 60 lists the activities that require Crypto-Asset Service Provider (CASP) authorisation in the EU. The two that matter for agent-commerce settlement are exchange of crypto-assets for funds (the USDC-to-EUR swap) and custody and administration of crypto-assets on behalf of clients (holding USDC for a customer, even briefly). Anyone executing those activities on behalf of EU clients needs to be authorised, full stop. That said, the regulation does not require the customer-facing API vendor to be the licensed entity β€” it requires that somebody in the settlement chain is licensed for each regulated activity. This is the basis for the technical-service-provider model. ## The two legal models in plain English Model 1: CASP-licensed vendor. The vendor itself holds the Article 60 authorisation, custodies customer USDC, executes the swap on its own book, and pays EUR from its own balance sheet. Examples: Bitstamp, Kraken EU, larger exchanges. Pros: single counterparty, single audit trail. Cons: 12-24 months and EUR 150k+ to obtain authorisation; ongoing capital, governance and reporting burden. Model 2: Technical service provider (TSP) behind licensed partners. The vendor never custodies customer funds. The customer-facing API orchestrates the flow but the actual swap and EUR payout are executed atomically by a licensed European payment partner on the partner's book. AsterPay is one example; many agent-commerce-native rails follow this pattern. Pros: ship in months not years, regulated perimeter is the partner's responsibility. Cons: need a robust partner contract, and the TSP must publicly disclose the model so customers know which entity holds the licence (partner names are typically disclosed to onboarded customers under partnership-only disclosure terms rather than on a public marketing page). Both models are MiCA-aligned. Both are routinely used by European fintechs in production today. The choice between them is a build-vs-buy question, not a legal question. ## Five questions to ask any stablecoin settlement vendor - Who holds the CASP licence that converts USDC to EUR for my settlements? Get the legal name, the Member State that authorised it, and the registration number on the ESMA register. - Does the vendor custody my funds or does the partner CASP do it? If the vendor custodies, they need their own CASP licence. If the partner does, get that contract chain in writing. - Show me the contractual chain. Your agreement with the vendor β†’ the vendor's agreement with the CASP partner β†’ the CASP partner's MiCA authorisation. All three documents should be reviewable. - What happens if the CASP partner is suspended or loses authorisation? Is there a documented fallback partner? How fast does failover take? Has it been tested? - What is your Travel Rule policy? EU Regulation 2023/1113 requires identifying information on transfers above EUR 1,000. Who collects it? Who reports? ## How AsterPay answers these ### AsterPay's MiCA position - Partner roster: Licensed European payment and crypto-asset partners under partnership-only disclosure. Specific partner identities are shared with onboarded customers under NDA, not on this page. - Custody model: AELIRA LTD (the AsterPay operator) never takes title to USDC; the partner custodies and converts on its own book. - Contractual chain: AELIRA LTD ↔ licensed partner β€” documentation available on request under NDA for prospective customers. - Failover model: Multi-partner routing across currencies (EUR settlement live; GBP and USD on the roadmap); auto-route based on currency, amount and partner availability. - Travel Rule: Activates above EUR 1,000; the licensed partner collects and reports; AsterPay passes the required identifiers in the settlement payload. - Disclosure: Public, in plain language, on every page of asterpay.io and in the API documentation. AsterPay does not hold a CASP licence in its own name and is not pursuing a CASP application. This is a deliberate commercial choice: the partner-routed model lets AsterPay ship a faster, cheaper, multi-currency rail than any single-CASP setup could, while keeping every actual money-movement event on a regulated entity's books. ## Is "MiCA-compliant" the right phrase? No. MiCA-compliant implies the speaker holds the licence and meets every obligation in their own name. MiCA-aligned is the honest phrase for a technical service provider routing through licensed partners. If a vendor calls itself "MiCA-compliant" without naming the entity that holds the licence, walk away β€” either they hold one and should be naming it, or they don't and the claim is misleading. AsterPay says "MiCA-aligned via licensed European payment and crypto-asset partners" precisely because that is the accurate description. ## What this means for AI agent commerce Most agent commerce today is settled in stablecoins because the on-chain transfer is fast and the agent doesn't have a bank account. But the merchant on the other end almost always wants EUR, USD or GBP β€” not USDC. The settlement layer is the bridge. Picking a MiCA-aligned bridge means your agent commerce stack survives the next round of EU enforcement actions, your finance team gets clean fiat-denominated journal entries, and your VAT calculations are not subject to FX drift between receipt and conversion. The TSP-behind-licensed-partners model is what makes agent commerce shippable in the EU today. Without it, every agent-commerce vendor would need to either spend two years getting its own CASP licence or move out of the EU. Neither is good for European builders, and neither is required by MiCA. ### Related guides - [EUR settlement for AI agents β€” buyer's guide](/learn/eur-settlement-for-ai-agents/) - [Best x402 facilitator in Europe β€” how to choose](/learn/best-x402-facilitator-europe/) - [How to convert agent stablecoin payments to EUR](/learn/how-to-convert-agent-stablecoin-payments-to-eur/) - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay is not affiliated with Aster (ASTER) DEX, the BNB Chain perpetual exchange, and has no native token. This page is an information guide, not legal advice. Consult your own counsel before signing a settlement agreement. --- # The MiCA 1 July 2026 deadline: what it means for crypto APIs and AI agent payments | AsterPay Source: Markdown mirror: > The MiCA transitional period ends 1 July 2026. After that, providing crypto-asset services to EU clients without a CASP licence is illegal. ~200 of 1,200+ firms are authorized. What it means for AI agent payments, stablecoin settlement and crypto APIs. [← Learn](/learn/) # The MiCA 1 July 2026 deadline: what it means for crypto APIs and AI agent payments By Petteri , Co-founder of AsterPay Β· Published: 15 June 2026 Β· Last updated: 15 June 2026 Β· 9 min read Answer The MiCA transitional period ends on 1 July 2026 . After that date, any firm providing crypto-asset services to EU clients without a MiCA CASP authorization is in breach of EU law and must cease or wind down. As of May 2026 only ~200 of 1,200+ legacy firms were authorized (about 17%). For AI agent payments and crypto APIs the practical rule is simple: any step that holds crypto or converts stablecoins to EUR must run through a licensed CASP. A non-custodial design that settles via a licensed EU partner stays on the right side of the line. ## What is the MiCA 1 July 2026 deadline? MiCA β€” the EU's Markets in Crypto-Assets Regulation β€” let member states grandfather existing crypto-asset service providers (CASPs) for up to 18 months while their full authorization applications were processed. That window closes everywhere on 1 July 2026. In its April 2026 statement, ESMA confirmed that after this date any entity providing crypto-asset services to EU clients without a MiCA licence β€” or a timely application filed before its national deadline β€” is in breach of EU law and must stop offering those services. There are no further extensions. ESMA also warned investors that not all providers will be authorized after 1 July, and told them to verify their provider on the ESMA Interim MiCA Register before transferring funds. The reckoning is not theoretical: national regulators are expected to enforce from day one. ## How many crypto firms are MiCA-authorized? Very few, relative to the starting population. The conversion rate is the story of MiCA's transition. | | Metric | Figure (as of May 2026) | Full MiCA CASP authorizations | ~200 (β‰ˆ194–210, incl. credit institutions), across 23 member states | Legacy VASP registrations pre-MiCA | 1,200+ (with the wider registered population estimated at 2,700–3,000) | Conversion rate | ~17–18% | EU jurisdictions with zero authorizations | 10 Authorized names include Bitvavo, Bitpanda, Kraken, Coinbase, Binance, Crypto.com and OKX (via Malta), Bitstamp (Luxembourg) and Revolut (via CySEC in Cyprus). The implication: a large majority of firms that operated in the EU under old national regimes will not be authorized when the deadline hits. ## What happens to firms without a MiCA licence after 1 July 2026? An unauthorized firm has five options, and four of them mean leaving the market as it stands today: - Obtain a licence β€” only realistic if an application was already filed before the national deadline. - Stop operating in the EU. - Run an orderly wind-down β€” ESMA expects a credible, immediately executable plan, with prior client notice, in place by 1 July 2026. - Transfer clients to an authorized CASP β€” migrate balances to a licensed provider or self-hosted wallets. - Merge with a licence holder. Penalties for non-compliance include administrative fines, public censure, suspension and withdrawal of authorization. Some jurisdictions go further: France has warned that unauthorized providers could face blacklisting, website blocking and criminal penalties. ## What does the deadline mean for AI agent payments and crypto APIs? If your product lets AI agents pay in stablecoins and you settle that value to a European business, the regulated act is the stablecoin-to-fiat conversion and any custody of crypto β€” and that act now needs a MiCA-authorized CASP behind it. The deadline draws a sharp line through the agent-payments space: - Pure-crypto rails with no EU licence (raw x402 setups, non-EU agent-payment networks) cannot legally provide the regulated service to EU clients once the transition ends. - EUR settlement becomes a licence-gated feature , not a commodity. Converting USDC to EUR for a merchant is exactly the activity MiCA regulates. - Demand shifts to compliant rails. The firms winding down still have clients and volume that must move to an authorized provider β€” a migration opportunity for whoever offers a compliant settlement path. ## Does an AI agent payment facilitator need its own MiCA licence? Not necessarily β€” but the structure has to be right. The authorization is needed by the legal entity that actually performs the regulated service to EU clients. A facilitator can stay compliant by being non-custodial and routing the regulated steps β€” custody and USDCβ†’EUR conversion β€” through a licensed EU CASP partner , while the facilitator itself provides only the technology and trust layer. The ESMA caveat to watch: a MiCA authorization applies only to the specific authorized legal entity β€” not to other companies in the same group β€” and custodial services cannot be outsourced to unlicensed entities , even within the same group. A genuinely non-custodial design, where the licensed partner is the entity that custodies and converts, is the clean answer: there is no custody to outsource, and the regulated activity sits with the authorized CASP. ## Which stablecoins are MiCA-compliant? | | Stablecoin | MiCA status in EU-regulated markets | USDC (Circle) | Authorized β€” MiCA-compliant e-money token | EURC (Circle) | Authorized β€” euro-denominated, MiCA-compliant | USDT (Tether) | Shut out β€” declined MiCA authorization; delisted from EU-regulated venues For agent payments that settle into EUR, building on MiCA-compliant stablecoins such as USDC and EURC avoids the risk of holding an asset that EU-regulated venues are required to delist. ## How AsterPay stays compliant by design AsterPay was built for this deadline rather than scrambling against it. The architecture is non-custodial : AsterPay never holds agent or merchant funds. The regulated steps β€” custody and stablecoin-to-EUR conversion β€” run through a licensed European partner , so the authorized entity performs the regulated activity while AsterPay provides the trust and settlement technology on top. - Non-custodial settlement β€” USDC/EURC to EUR via SEPA Instant, executed by a licensed EU partner; AsterPay does not touch custody. - MiCA-compliant assets only β€” USDC and EURC, never USDT. - Trust and AML controls β€” [Know Your Agent (KYA)](/learn/know-your-agent-compliance-eu/) screening on the paying agent, sanctions checks in under 100ms, and the MiCA Travel Rule automated for transfers over EUR 1,000. - Audit-grade trail β€” every settlement produces a verifiable record for the compliance evidence regulators expect. ## Checklist: what to do before 1 July 2026 - Identify which legal entity performs each regulated step in your flow, and confirm it is on the ESMA Interim MiCA Register. - Ensure stablecoin custody and conversion run through a licensed CASP β€” not an unlicensed group affiliate. - Move off non-compliant stablecoins (e.g. USDT) toward USDC / EURC . - Confirm Travel Rule and sanctions screening are in place for crypto transfers. - If you are unauthorized, execute a wind-down or migrate clients to a licensed provider before the deadline. ### Need a compliant EUR settlement rail? AsterPay settles agent stablecoin payments to EUR via a licensed EU partner β€” non-custodial, MiCA-aligned, Travel-Rule automated. [Create a free account β†’](https://app.asterpay.io/signup) PL Petteri Co-founder of AsterPay (AELIRA LTD). Building the EU-native trust and EUR-settlement layer for AI agent commerce. [@Asterpayment](https://x.com/Asterpayment) ## Related reading - [MiCA-aligned stablecoin settlement](/learn/mica-aligned-stablecoin-settlement/) - [Know Your Agent (KYA) compliance in Europe](/learn/know-your-agent-compliance-eu/) - [How to convert agent stablecoin payments to EUR](/learn/how-to-convert-agent-stablecoin-payments-to-eur/) - [How do AI agents pay merchants?](/learn/how-ai-agents-pay-merchants/) - [The best x402 facilitator in Europe](/learn/best-x402-facilitator-europe/) ### References - ESMA. "Statement on the end of transitional periods under MiCA" (April 2026) β€” transitional period expires 1 July 2026; wind-down expectations. - European Commission. "Markets in Crypto-Assets Regulation (MiCA)", Regulation (EU) 2023/1114, and the Travel Rule under Regulation (EU) 2023/1113. - CCN. "July 1 MiCA Deadline Approaches: Over 80% of EU Crypto Firms Risk Being Forced Out" (June 2026) β€” ~210 CASPs authorized vs 1,200+ legacy VASPs. - The Crypto Times. "15 days to MiCA: 75% of EU crypto firms race against July 1 cutoff" (15 June 2026). - Hogan Lovells. "As MiCA's deadline approaches, Europe's crypto market faces a reckoning" (2026) β€” pre-MiCA population of 3,000+ VASPs. - Citium Tech. "MiCA compliance deadline tracker: key dates for 2026." Have a correction or want this page to cover a different angle? Email [petteri@asterpay.io](mailto:petteri@asterpay.io). We update this page as the register and enforcement evolve. --- # What is an x402 facilitator? β€” Definitive guide | AsterPay Source: Markdown mirror: > An x402 facilitator is the trusted party that verifies and settles HTTP 402 stablecoin payments for AI agents. Coinbase CDP, AsterPay and the rest of the landscape, explained. [← Learn](/learn/) # What is an x402 facilitator? By Petteri , Co-founder of AsterPay Β· Last updated 23 April 2026 Β· 4 min read Answer An x402 facilitator is the trusted party that verifies an agent's HTTP 402 payment proof and executes the on-chain settlement, then forwards the result to the resource server. The default Coinbase CDP facilitator handles USDC on Base. EU-native facilitators like AsterPay add EUR conversion (USDC to EUR via SEPA Instant), KYA trust scoring and ERC-8004 identity attestation on top of the standard x402 flow. ## Why do you need a facilitator at all? Because the resource server β€” the API offering paid endpoints β€” does not want to run blockchain infrastructure, hold private keys, or carry compliance responsibility for moving stablecoins. The facilitator absorbs all of that. The merchant only needs to (a) return HTTP 402 with the right headers and (b) forward one HTTP request to the facilitator. When the facilitator confirms settlement, the merchant returns the API response. That is the entire integration. ## What does a facilitator actually do? The x402 specification defines two endpoints that every facilitator must expose: - `POST /verify` β€” checks the EIP-712 signature on the agent's payment payload, confirms the asset and amount match the original 402, validates the recipient and chain. - `POST /settle` β€” submits the EIP-3009 `transferWithAuthorization` to the chain, waits for finality, returns a transaction hash and a receipt. Some facilitators (AsterPay being the canonical example) chain a third step transparently: convert the USDC to EUR via licensed CASP partners and push a SEPA Instant payout to the merchant's IBAN, all within the same `/settle` call. The merchant sees a single 200 OK with a Payment-Receipt header containing both the on-chain tx hash and the SEPA reference. ## How do facilitators differ? | | Dimension | Coinbase CDP | AsterPay | Self-hosted | Settlement currency | USDC only | USDC + EUR + GBP + USD | USDC (DIY EUR) | Chains | Base, Polygon | Base, ETH, Polygon, Arb, OP, Lightning | Whatever you wire | Regulation | US-regulated | EU CASP partners (MiCA), KYB via Sumsub | Your problem | Trust scoring | No | KYA v1, 0-100 score, sanctions screening | No | Latency (P95) | ~3 sec (USDC only) | ~10 sec (full EUR settlement) | Depends | Self-serve | Yes | Yes | Yes ## Can I run my own facilitator? Yes. The reference implementation is open source at [github.com/coinbase/x402](https://github.com/coinbase/x402). Self-hosting is appropriate for high-volume merchants who want full control of latency, routing and fees. The trade-off: you are now responsible for compliance (MiCA in the EU; FinCEN/state MTL in the US), fraud monitoring, chain operations and 24/7 on-call. Most teams use a hosted facilitator for the same reason they use Stripe instead of building a card processor β€” the differentiation is in the product, not the rail. ## Which facilitator should I pick? - Just need USDC on Base? β†’ Coinbase CDP. Free at the protocol layer, well-documented, the canonical implementation. - EU merchant who needs EUR in your bank? β†’ AsterPay. The only facilitator with native SEPA Instant settlement and MiCA-aligned partner CASP routing. - Need on-chain reputation and trust scoring? β†’ AsterPay's KYA layer is the only production trust scorer for x402 right now. - Hyperscaler treasury or paranoid about counterparty risk? β†’ Self-host the reference facilitator and own the full stack. ### Related - β†’ [What is x402?](/learn/what-is-x402/) - β†’ [What is x402 EUR settlement? (pillar guide)](/learn/what-is-x402-eur-settlement/) - β†’ [What is KYA?](/learn/what-is-kya/) - β†’ [How AsterPay compares](/compare/) --- # What is KYA (Know Your Agent)? β€” Trust framework for AI agent payments | AsterPay Source: Markdown mirror: > KYA (Know Your Agent) is the agent-payments equivalent of KYC. AsterPay [← Learn](/learn/) # What is KYA (Know Your Agent)? By Petteri , Co-founder of AsterPay Β· Last updated 23 April 2026 Β· 5 min read Answer KYA stands for Know Your Agent. It is AsterPay's open trust-scoring framework for AI agent wallets in payment flows. Every agent address gets a score from 0 to 100 across seven components β€” wallet age, wallet activity, sanctions screening, ERC-8004 identity, operator KYB, transaction history and trust bond β€” mapped to five payment tiers. KYA is the agent-payments equivalent of KYC for humans. ## Why do agent payments need KYA? Because AI agents can spin up new wallets at zero cost and scale fraud horizontally faster than any human attacker. Traditional KYC assumes a human identity behind a card; that assumption breaks for autonomous software. KYA replaces "who is the person?" with " what is the operational reputation of this wallet? " β€” sanctions clean, age, activity, ERC-8004 attested, KYB-verified operator, transaction history, posted bond. ## How is the KYA score calculated? The seven components and their weights (full v1 schema at [/.well-known/kya-schema-v1.md](/.well-known/kya-schema-v1.md)): | | Component | Weight | What it measures | Wallet age | 10 | Time since first on-chain activity. Brand-new wallets score zero here. | Wallet activity | 10 | Volume and recency of legitimate-looking transactions. | Sanctions clean | 20 | OFAC / EU / UN / Chainalysis sanctions screening on every connected address. | ERC-8004 identity | 15 | On-chain agent identity registered, with metadata and operator binding. | Operator KYB | 15 | Human or company behind the agent has completed KYB through Sumsub or equivalent. | Transaction history | 15 | Settlement success rate, dispute rate, refund rate over the agent's lifetime. | Trust bond | 15 | Optional posted USDC bond that gets slashed on confirmed bad behavior. ## What are KYA tiers? | | Tier | Score | Permissions | Unknown | 0-19 | Read-only API access. Free endpoints only. | Basic | 20-39 | Small transactions (< $100 / day cap). | Verified | 40-59 | Standard transactions, EUR settlement enabled. The production default. | Trusted | 60-79 | Higher limits, priority settlement queue. | Enterprise | 80-100 | Custom limits, EUR + GBP + USD, dedicated support. ## How do I check an agent's KYA score? Free GET request, no auth, no rate limit for reasonable use: ``` curl https://x402.asterpay.io/v1/agent/trust-score/0xYourAgent { "success": true, "data": { "address": "0x...", "score": 72, "tier": "trusted", "blocked": false, "components": { "walletAge": 8, "walletActivity": 7, "sanctionsClean": 20, ... }, "sanctions": { "clean": true, "provider": "chainalysis" }, "limits": { "maxPerTx": 5000, "maxDaily": 25000 } } } ``` Batch checks for up to 50 addresses are also free at `POST /v1/agent/trust-score/batch`. The deeper paid endpoint `/v1/agent/deep-analysis/{address}` ($0.01) returns the full historical breakdown including sub-component evidence. ## Is KYA open? Yes. The KYA v1 schema is published openly at [/.well-known/kya-schema-v1.md](/.well-known/kya-schema-v1.md) and the scoring rubric is documented on this page. AsterPay's intention is for KYA to be adopted by other facilitators and merchants as the default trust language for agent commerce β€” much like FICO became the default credit-score language without being owned by a single bank. The schema is versioned, comment-period-driven and open to community PRs. ## How does KYA fit in the EU AI Act? The EU AI Act classifies AsterPay's KYA layer as a limited-risk system under Article 50 (transparency obligations). Concretely: when KYA scoring affects a payment decision, the affected party (merchant or agent operator) is entitled to know that an AI/algorithmic system was involved and to an explanation of the factors. KYA's seven-component breakdown is the explanation β€” by design. ### Related - β†’ [ERC-8004 explained β€” on-chain agent identity](/learn/erc-8004-explained/) - β†’ [What is x402 EUR settlement?](/learn/what-is-x402-eur-settlement/) - β†’ [KYA framework schema](/.well-known/kya-schema-v1.md) - β†’ [KYA v1 schema (machine-readable)](/.well-known/kya-schema-v1.md) --- # What is x402 EUR settlement? β€” Definitive guide for AI agent payments | AsterPay Source: Markdown mirror: > x402 EUR settlement converts an AI agent [← Learn](/learn/) # What is x402 EUR settlement? A definitive guide for AI agent payments By Petteri , Co-founder of AsterPay Β· Published: 23 April 2026 Β· Last updated: 23 April 2026 Β· 9 min read Answer x402 EUR settlement is the process of converting an AI agent's HTTP 402 stablecoin payment (USDC, EURC or EURCV) into euros in a merchant's bank account via SEPA Instant β€” as one continuous flow. The agent pays on-chain; the merchant receives off-chain euros in under 10 seconds. As of April 2026, AsterPay (AELIRA LTD, EU) is the only production x402 facilitator offering native EUR EUR settlement. ## What is x402? x402 is an open payment protocol that revives the long-dormant HTTP 402 "Payment Required" status code for the era of autonomous AI agents. Originally proposed by Coinbase in 2025, x402 lets any HTTP API request payment from a client agent in stablecoins, on-chain, in a single round-trip. The agent receives a 402 response containing payment requirements; it submits a signed payment proof in a follow-up header; the resource server forwards the proof to a facilitator for verification and settlement, then returns the actual response. The protocol's core innovation is that it removes credit-card-era assumptions β€” no merchant accounts, no card-network fees, no chargebacks, no human-in-the-loop. An AI agent can discover, pay and consume an API in a few hundred milliseconds. Today x402 is supported by Coinbase CDP, Tempo, Stripe (via the parallel MPP / Machine Payments Protocol), and an ecosystem of facilitators including [AsterPay](https://asterpay.io) in the EU. ## What does "EUR settlement" mean? In payments, settlement is the moment money lands in the merchant's account in spendable form. For an x402 payment that means the difference between two outcomes: - USDC settlement (default Coinbase CDP) β€” the merchant receives USDC on Base. They still need to convert it to EUR somewhere else (an exchange, a CASP, an OTC desk) before they can pay rent or salaries. - EUR settlement (AsterPay) β€” the merchant receives EUR on their bank account, with a SEPA reference, ready for accounting and VAT. The conversion happens inside the same x402 flow, automatically. For European merchants this is the difference between "I now have to do crypto bookkeeping" and "I don't even need to know my customer was an agent." The x402 EUR-settlement layer is the operational seam between agent-native commerce and Continental European banking. ## Why do AI agent payments need EUR settlement? European merchants invoice in euros, file VAT in euros, and pay salaries in euros. An on-chain stablecoin payment is great for the agent but creates three problems for the merchant: - Accounting friction β€” every USDC inflow needs an EUR-equivalent valuation at the time of receipt, plus a separate journal entry when it is later converted. Multiply by hundreds of agent-driven micropayments per day and the bookkeeping is unviable. - VAT timing risk β€” under EU VAT rules, the taxable event is the moment of supply in EUR. If the merchant converts USDC days later at a different rate, the VAT base shifts and reconciliations get messy. - Treasury exposure β€” even EUR-denominated stablecoins like EURC carry counterparty risk that most SMEs are not equipped to evaluate. EUR settlement collapses all three problems into a single flow: the agent pays USDC; the merchant sees EUR on their bank statement; the SEPA reference includes the original x402 payment ID for one-click reconciliation. ## How does USDC β†’ SEPA Instant work in practice? Here is the actual flow inside an AsterPay-facilitated x402 payment, end to end: ``` 1. Agent calls GET https://merchant.example.com/api/data 2. Merchant API β†’ returns HTTP 402 + WWW-Authenticate: Payment header (facilitator: x402.asterpay.io, asset: USDC on Base, 0.05 USDC) 3. Agent signs a USDC permit + sends payment header 4. Merchant API β†’ forwards proof to AsterPay /v2/x402/settle 5. AsterPay a) verifies signature on Base b) auto-routes USDC β†’ EUR via best CASP partner of 4 c) pushes EUR via SEPA Instant to merchant IBAN d) returns 200 OK + Payment-Receipt header 6. Merchant API β†’ returns the actual API response to the agent 7. Total elapsed time: ~7 seconds (P50), ~10 seconds (P95) ``` The merchant never holds USDC. The agent never holds EUR. AsterPay is non-custodial β€” funds pass through licensed CASP partners under MiCA, never sitting on AsterPay's balance sheet. The whole flow is a single HTTP retry from the agent's perspective. ## Who runs x402 EUR facilitators today? As of April 2026 the landscape is small but consolidating. Here is a snapshot: | | Facilitator | EUR via SEPA | x402 verify | EU regulated | KYA trust scoring | Self-serve | AsterPay (AELIRA LTD) | Yes β€” SEPA Instant | Yes β€” full x402+MPP | Yes β€” MiCA via CASP partners; CASP-direct in 2026 | Yes β€” KYA v1 schema | Yes | Coinbase CDP (default) | No β€” USDC only | Yes | US-regulated; no EU CASP | No | Yes | BVNK | Yes | No β€” not an x402 facilitator | EMI-licensed | No | Sales-led | Raw x402 (self-host) | No | Yes | DIY | DIY | Yes Source: AsterPay competitive landscape audit, April 2026. See [/compare](/compare/) for the full side-by-side methodology. ## Is x402 EUR settlement regulated under MiCA? Yes. EUR settlement of stablecoin payments falls within the scope of the EU's Markets in Crypto-Assets Regulation (MiCA) , which entered full application in December 2024. Two activities are clearly captured: - Exchange of crypto-assets for funds β€” the USDC-to-EUR swap is a regulated CASP service. - Custody and administration of crypto-assets β€” applies if the facilitator holds the agent's stablecoin even momentarily. AsterPay's architecture is intentionally non-custodial : the swap is executed atomically through licensed CASP partners; AsterPay never takes title to the USDC. This places the regulatory burden on the partners (who are already authorised) and lets AsterPay operate as a payment-orchestration layer while operating as a technical service provider behind partner authorisations. The full regulatory map for AsterPay's 2026 roadmap is documented in the [MiCA-aligned stablecoin settlement guide](/learn/mica-aligned-stablecoin-settlement/). ## How much does x402 EUR settlement cost? AsterPay's published pricing for the EUR-settlement layer is: - 0.50% (50 bps) on the EUR settlement amount, billed to the merchant. - + underlying CASP partner spread , typically 30-80 bps depending on volume and currency pair. Surfaced transparently in the `/v1/settlement/estimate` response. - No monthly fees, no per-transaction KYC fees, no SEPA Instant surcharge, no setup fees. For comparison, Stripe's standard European card pricing is 1.4% + €0.25 for European cards and 2.5% + €0.25 for non-European cards, plus an FX markup of roughly 2% if the customer pays in a currency other than EUR β€” and settlement still takes 2-7 days. PayPal sits at 2.49% + fixed fee. Raw x402 via Coinbase CDP is essentially free at the protocol layer but leaves the EUR conversion as the merchant's problem. ## How long does USDC to EUR via SEPA Instant take? End-to-end latency in production is under 10 seconds (P95) . The breakdown: - USDC settlement on Base: 2-4 seconds (block finality). - CASP swap USDC β†’ EUR: 1-3 seconds. - SEPA Instant push to merchant IBAN: 1-3 seconds. SEPA Instant operates 24/7/365 across all 36 EU/EEA countries, including weekends, evenings and bank holidays. Since the European Commission's Instant Payments Regulation entered force in January 2025, every euro-area bank is required to offer SEPA Instant with the same fee as a regular SEPA credit transfer β€” which removed the last commercial obstacle to instant euro payouts. ## What chains and stablecoins does AsterPay accept? AsterPay's x402 facilitator accepts payments on five EVM chains with native USDC and on Bitcoin Lightning: | | Chain | Stablecoins | Status | Base | USDC, EURC | Live (primary) | Ethereum mainnet | USDC, EURC, EURCV | Live | Polygon | USDC | Live | Arbitrum | USDC | Live | Optimism | USDC | Live | Bitcoin Lightning | BTC (sats) | Live (via @asterpay@getalby.com) | Solana | USDC | Roadmap ## How do I integrate x402 EUR settlement? Three integration paths, in order of complexity: - MCP server β€” `npm install @asterpay/mcp-server`. Works with any LLM agent that speaks Model Context Protocol (Claude, GPT-5, Gemini agents). 12 commerce tools out of the box, no API key. - Python SDK β€” `pip install asterpay`. Three lines: instantiate, call endpoint, get EUR receipt. - Direct HTTP API β€” `https://x402.asterpay.io`. Full Swagger/OpenAPI at [/docs](https://x402.asterpay.io/docs). Free endpoints (KYA trust score, settlement estimate) require no auth. A merchant onboarding takes about 10 minutes through Sumsub KYB; after that, payouts run automatically with no per-transaction KYC and no manual off-ramp. ### Try it without writing code Get an EUR settlement estimate for any USDC amount β€” no signup required. [Get a $100 β†’ EUR estimate β†’](https://x402.asterpay.io/v1/settlement/estimate?amount=100) PL Petteri Co-founder of AsterPay (AELIRA LTD). Building the EU-native x402 facilitator for AI agent commerce. Previously fintech / payments infrastructure. [@Asterpayment](https://x.com/Asterpayment) ## Related reading - [What is x402? β€” protocol explainer](/learn/what-is-x402/) - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - [What is KYA (Know Your Agent)?](/learn/what-is-kya/) - [ERC-8004 explained β€” on-chain agent identity](/learn/erc-8004-explained/) - [EUR settlement for AI agents β€” buyer's guide](/learn/eur-settlement-for-ai-agents/) - [How AsterPay compares β€” Stripe, Wise, BVNK, raw x402](/compare/) - [MiCA-aligned stablecoin settlement β€” AsterPay's regulatory roadmap](/learn/mica-aligned-stablecoin-settlement/) ### References - Coinbase. "x402 Protocol Specification" (2025). [github.com/coinbase/x402](https://github.com/coinbase/x402) - European Commission. "Markets in Crypto-Assets Regulation (MiCA)", Regulation (EU) 2023/1114, in force 30 December 2024. - European Commission. "Instant Payments Regulation", Regulation (EU) 2024/886, in force 9 January 2025. - Stripe. "Machine Payments Protocol (MPP) specification" (2025). [mpp.dev](https://mpp.dev) - ERC-8004 β€” Agent Identity Standard. [eips.ethereum.org/EIPS/eip-8004](https://eips.ethereum.org/EIPS/eip-8004) - AsterPay. ".well-known/x402.json capability manifest" (April 2026). [asterpay.io/.well-known/x402.json](https://asterpay.io/.well-known/x402.json) - AsterPay. "KYA Trust Score schema v1" (April 2026). [asterpay.io/.well-known/kya-schema-v1](https://asterpay.io/.well-known/kya-schema-v1) Have a correction or want this page to cover a different angle? Email [samantha@asterpay.io](mailto:samantha@asterpay.io). We update this page every quarter. --- # What is x402? β€” HTTP 402 protocol for AI agent payments | AsterPay Source: Markdown mirror: > x402 is an open payment protocol that revives HTTP 402 [← Learn](/learn/) # What is x402? By Petteri , Co-founder of AsterPay Β· Last updated 23 April 2026 Β· 4 min read Answer x402 is an open payment protocol that uses the HTTP 402 "Payment Required" status code to let AI agents pay for API access in stablecoins, on-chain, in a single round-trip. Originally proposed by Coinbase in 2025, x402 is now supported by Coinbase CDP, Tempo, Stripe (via the parallel MPP standard) and an ecosystem of facilitators including AsterPay in the EU. ## Where does x402 come from? HTTP 402 has existed in the HTTP specification since 1997 (RFC 2068) but was reserved "for future use" β€” for almost three decades it had no canonical wire format. Coinbase published the [x402 specification](https://github.com/coinbase/x402) in 2025 to give that status code a concrete semantics for the era of autonomous AI agents, where API consumers are software, not humans, and the natural unit of payment is a stablecoin transfer rather than a card swipe. ## How does the x402 flow work? A complete x402 request-response cycle looks like this: ``` 1. Agent β†’ API: GET /api/data 2. API β†’ Agent: HTTP 402 Payment Required WWW-Authenticate: Payment realm="api.example.com" PAYMENT-REQUIRED: { asset: USDC, amount: 5000, network: base, recipient: 0x... } 3. Agent signs an EIP-3009 USDC transferWithAuthorization 4. Agent β†’ API: GET /api/data PAYMENT-SIGNATURE: 5. API β†’ Facilitator: POST /verify + /settle 6. Facilitator settles the USDC on-chain (~2-4s on Base) 7. API β†’ Agent: 200 OK + actual response + Payment-Receipt header ``` The whole flow is one HTTP retry from the agent's perspective. There is no merchant account, no card network, no chargeback window. The facilitator can be the canonical Coinbase CDP facilitator (USDC on Base) or any compliant alternative β€” for example [AsterPay's EU facilitator](https://x402.asterpay.io) that adds EUR EUR settlement on top. ## What problem does x402 solve? Card networks were designed for human checkout. They assume a person fills in a form, accepts a fee, possibly gets called by a bank to confirm. None of that fits an autonomous agent that needs to call ten APIs in 200 milliseconds to answer a single user prompt. x402 collapses the payment into the same HTTP round-trip as the API call itself: pay-per-call, sub-second, with no merchant-side integration beyond returning a 402. ## What is the difference between x402 and MPP? x402 (Coinbase) and MPP β€” the Machine Payments Protocol from Stripe and Tempo β€” are two parallel open standards that both use HTTP 402. The wire formats differ slightly: | | | x402 | MPP | Initiated by | Coinbase | Stripe / Tempo | 402 header | `PAYMENT-REQUIRED` | `WWW-Authenticate: Payment` | Settlement header | `PAYMENT-SIGNATURE` | `Authorization: Payment` | Default facilitator | Coinbase CDP | Stripe / open | Schemes | exact, lightning | exact, mpp-v1 Most production servers, including AsterPay, return both headers in every 402 response so an agent can use whichever SDK it already has installed. The two standards are converging in practice; the differences are skin-deep. ## What chains and stablecoins does x402 support? The x402 "exact" scheme works on any EVM chain with an EIP-3009 USDC implementation. Production support today: Base (primary), Ethereum mainnet, Polygon, Arbitrum and Optimism. The Solana scheme is in active development. Bitcoin Lightning is supported via a separate scheme using BOLT11 invoices β€” AsterPay runs a live Lightning x402 endpoint at `@asterpay@getalby.com`. ## Who runs x402 in production? - Coinbase CDP β€” the default facilitator for USDC on Base. - AsterPay β€” EU-native facilitator with EUR settlement via SEPA Instant. - Tempo β€” Stripe-backed payments network with native MPP/x402 support. - Bazaar β€” Coinbase's auto-discovery directory of x402-enabled APIs. ## How do I get started with x402? - As an agent : `npm install @x402/fetch` or `pip install x402`. Wrap your fetch client with `wrapFetchWithPayment` and you are done β€” 402s become automatic on-chain payments. - As a merchant : install an x402 middleware (Express, Fastify, FastAPI, Next.js all have community packages) and configure your facilitator. Five lines of code and your endpoint accepts agent payments. - As an EU merchant who needs EUR : point your facilitator at [x402.asterpay.io](https://x402.asterpay.io). Same flow, EUR lands in your bank. ### Related - β†’ [What is x402 EUR settlement? (pillar guide)](/learn/what-is-x402-eur-settlement/) - β†’ [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - β†’ [ERC-8004 explained](/learn/erc-8004-explained/) - β†’ [How AsterPay compares](/compare/) --- # x402 facilitator fees compared (2026) β€” who charges what | AsterPay Source: Markdown mirror: > What x402 facilitators actually charge in 2026: Coinbase CDP (free, USDC-only), Dexter (~0.1-0.5%), PayAI, Stripe (preview) and AsterPay ($0 facilitation, 0.5% + €0.10 only on EUR bank settlement). Fee table and how to read it. [← All guides](/learn/) # x402 facilitator fees compared (2026) Updated 15 July 2026 Β· 5 minute read Β· By Petteri, Co-founder Short answer Base facilitation β€” verifying an x402 payment proof and settling USDC on-chain β€” is free or near-free everywhere in 2026. Coinbase CDP set the precedent at $0; AsterPay matches it at $0 forever; Dexter charges roughly 0.1–0.5%. The fees that actually matter sit one layer up: getting fiat into a bank account, screening the paying agent, and compliance. That is where facilitators differ, and where you should compare. ## The fee table | | Facilitator | Facilitation fee (verify + on-chain settle) | Fiat settlement | What you actually pay for | Coinbase CDP | $0 | None β€” USDC stays on-chain | Nothing at facilitator level; off-ramp yourself (e.g. Coinbase exchange fees) | AsterPay | $0 forever, no API key | EUR via SEPA Instant: 0.5% + €0.10 (EU rail); 1.5% + €1.00 (US rail) | EUR in your bank <10 s, per-call KYA + sanctions screening, MiCA-aligned path | Dexter | ~0.1–0.5% | None β€” stablecoins on-chain | Highest-volume infrastructure, Solana-native, agent-to-agent routing | PayAI | Varies by flow | None published | Crypto-native agent payment flows | Stripe (preview) | Not public | Stripe balance β†’ payout (US preview only) | Stripe ecosystem integration β€” when it ships in your region Sources: public pricing pages and tracked facilitator data (Signal402), July 2026. Negotiated enterprise terms may differ. ## How to read this table ### 1. Facilitation is a commodity β€” treat $0 as the baseline Verifying an EIP-3009 signature and broadcasting a transfer costs the facilitator close to nothing, so competition drove the price to zero. If a facilitator charges a percentage just to verify and settle on-chain, you are paying for their distribution, not their work. AsterPay's position is explicit: facilitation is free forever , with no API key and no volume tiers, and revenue comes from the value layer only. ### 2. The real comparison is the value layer Ask what happens after the USDC settles on-chain. If the answer is "nothing, that's your problem" β€” the facilitator is free but your finance team inherits an off-ramp project: exchange accounts, FX spreads, accounting for crypto on the balance sheet, and a compliance story to write. A 0% facilitation fee plus a DIY off-ramp typically costs an EU merchant more, in fees and hours, than 0.5% + €0.10 for euros arriving automatically. ### 3. Screening is either in the payment path or it isn't None of the free crypto-native facilitators screen the paying agent. For many workloads that's fine. For an EU business taking real revenue from autonomous buyers, an unscreened inflow of anonymous stablecoins is a problem you eventually answer for. AsterPay runs KYA trust scoring and Chainalysis sanctions screening on every payment before settlement β€” that cost is inside the 0.5%, not an add-on. ## Worked example: 10,000 agent payments of $0.50 | | Stack | Facilitation | Getting EUR to bank | Total cost | CDP + DIY off-ramp | $0 | Exchange fees ~0.5–1% + FX spread + your hours | ~€30–60 + finance-team time | Dexter (stay on-chain) | ~$5–25 | Not solved β€” USDC remains on-chain | $5–25 and no euros yet | AsterPay EU rail | $0 | 0.5% + €0.10 per settled payout batch | ~€25 + €0.10/payout, euros in bank, screening included Illustrative β€” assumes daily batched payouts; exact numbers depend on batching and volumes. ### Bottom line Don't compare facilitation fees β€” they're all at or near zero and heading there permanently. Compare what it costs to get from "agent paid USDC" to "clean euros in my bank account with a compliance story". On that comparison, published prices in 2026 put AsterPay's EU rail at 0.5% + €0.10 all-in, screening included. ### Related reading - [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - [Best x402 facilitator in Europe: how to choose](/learn/best-x402-facilitator-europe/) - [AsterPay vs Coinbase CDP](/compare/asterpay-vs-coinbase-cdp/) - [AsterPay vs Dexter](/compare/asterpay-vs-dexter/) - [AsterPay vs Stripe (x402 + MPP)](/compare/asterpay-vs-stripe-x402-mpp/) AsterPay is operated by AELIRA LTD (Cyprus, HE 490977). AsterPay has no native token. Competitor fees are from public pricing pages and tracked facilitator data as of July 2026 and may change or differ for negotiated accounts. This page is informational. --- # x402 vs MPP β€” which agent payment protocol should you support? | AsterPay Source: Markdown mirror: > x402 (Coinbase) settles in USDC on-chain; MPP (Stripe/Tempo) settles over fiat rails. Side-by-side comparison of the two HTTP 402 agent payment protocols β€” and why APIs increasingly accept both. [← Learn](/learn/) # x402 vs MPP β€” which agent payment protocol should you support? By Petteri , Co-founder of AsterPay Β· Last updated 9 June 2026 Β· 5 min read Answer Both are HTTP 402 payment protocols for AI agents, but they settle on different rails. x402 (Coinbase) settles in stablecoins on-chain β€” typically USDC on Base. MPP , the Machine Payments Protocol (an open standard from Stripe and Tempo), settles over fiat and PSP rails. They are not mutually exclusive: a single 402 response can advertise both, and dual-protocol facilitators like AsterPay accept either on every paid endpoint. ## The 30-second history x402 revived the dormant HTTP 402 "Payment Required" status code in 2025 as a machine-payable standard: the server replies 402 with an `accepts` array describing how to pay (asset, chain, amount, recipient), the agent signs an EIP-3009 `transferWithAuthorization`, and a facilitator verifies and settles it on-chain. Coinbase published the reference implementation and runs the default facilitator. MPP (Machine Payments Protocol) arrived from the fiat side: an open standard from Stripe and the Tempo ecosystem that uses the same 402 handshake but replaces on-chain transfers with payment tokens that clear over conventional PSP infrastructure. An agent with access to a funded MPP wallet or card-rail backing can pay without touching a blockchain. ## Side-by-side comparison | | Dimension | x402 | MPP | Origin | Coinbase (open spec) | Stripe + Tempo (open spec) | Settlement rail | On-chain β€” USDC on Base (also ETH L2s, Solana) | Fiat / PSP rails, payment tokens | Typical asset | USDC, EURC stablecoins | USD / fiat balances | Finality | ~2–3 s on Base | PSP authorization, payout per schedule | Micropayment floor | Sub-cent viable ($0.001 works) | PSP minimums apply | Agent wallet needed | Crypto wallet + USDC balance | MPP-enabled account (e.g. Stripe-issued) | Chargebacks | None (refund protocols layer on top) | PSP dispute rules | Live ecosystem today | x402 Bazaar, x402scan, thousands of endpoints | Growing via Stripe merchant network ## Why "both" is the right answer for API sellers The protocols compete for the same HTTP handshake but serve different agent populations. Crypto-native agents hold USDC and pay via x402 today. Enterprise agents wired into Stripe-style billing will arrive with MPP credentials. Since one 402 response can carry both header sets side by side, advertising both costs nothing and roughly doubles your addressable demand. AsterPay runs this dual-protocol pattern in production: every paid endpoint at [x402.asterpay.io](https://x402.asterpay.io) accepts both x402 and MPP , and the [MPP method advertisement](https://x402.asterpay.io/.well-known/mpp-methods.json) is published alongside the [x402 discovery document](https://asterpay.io/.well-known/x402.json). ## What about EUR settlement? Neither protocol pays your European suppliers in euros by itself. With x402 the merchant ends up holding USDC; with MPP the funds sit at the PSP. AsterPay closes the last mile for both: USDC from x402 payments is converted and pushed to the merchant's IBAN via SEPA Instant in under 10 seconds, and MPP-side flows are normalized into the same EUR payout pipeline. One integration, two protocols, euros in the bank. ## Decision guide - Selling API calls to AI agents today? β†’ Support x402 first (largest live agent population), add MPP via a dual-protocol facilitator. - Enterprise customers on Stripe billing? β†’ MPP support future-proofs you; you keep one 402 handshake for both. - European merchant who needs EUR, not USDC? β†’ Use a facilitator with native EUR settlement (AsterPay is the only one combining dual-protocol acceptance with SEPA Instant payout and KYA trust scoring). - Building an agent that pays? β†’ Read the 402 response's options and support whichever rails your treasury holds; x402 needs a funded USDC wallet, MPP needs an MPP-enabled account. ### Related - β†’ [What is x402?](/learn/what-is-x402/) - β†’ [What is an x402 facilitator?](/learn/what-is-an-x402-facilitator/) - β†’ [What is x402 EUR settlement? (pillar guide)](/learn/what-is-x402-eur-settlement/) - β†’ [How AsterPay compares](/compare/) --- # AsterPay MCP Connector β€” read-only tools for AI assistants Source: Markdown mirror: > Connect Claude and other AI assistants to AsterPay [AsterPay](/) [Docs](/docs/) [Home](/) Model Context Protocol # AsterPay MCP connector Give Claude and other AI assistants four read-only AsterPay tools: agent trust scoring, USDCβ†’EUR settlement estimates, crypto market rates, and merchant payment-endpoint resolution. No API key. Nothing moves money. ## What it is A hosted, remote MCP server at `https://mcp-api.asterpay.io/mcp` exposing AsterPay's public data as assistant tools. It is read-only and unauthenticated β€” there is no payment, budget, or money-movement capability here. (Those live in the separate `@asterpay/mcp-server` npm package for developers who wire up a wallet.) ## Tools ### check_agent_trust Know Your Agent: trust score 0–100, tier (Open/Verified/Trusted/Enterprise) and components (ERC-8004 identity, sanctions screening, wallet age/activity) for an Ethereum address. read-only ### settlement_estimate Estimate converting a USDC amount to EUR: exchange rate, AsterPay fee (0.5% + €0.10 on the EU rail), net EUR, and SEPA Instant timing. An estimate only β€” no payment is made. read-only ### market_rates Current reference market rates AsterPay uses (e.g. USDC, EURC and major crypto rates). No input. read-only ### merchant_resolve Resolve a European business to its verified payment endpoint (IBAN/BIC) from provable sources. By merchant id, or business id + type (vat, y_tunnus, company_number, lei, duns). read-only ## Connect it in Claude From the Connectors Directory (once listed): open Claude β†’ Connectors β†’ find β€œAsterPay” β†’ Connect. No credentials are required. As a custom connector (available today): in Claude, add a custom connector with this URL: ``` https://mcp-api.asterpay.io/mcp ``` The transport is Streamable HTTP. There is no sign-in step β€” connect and the four tools appear. ## Example prompts - β€œUse AsterPay to check the trust score of wallet `0xd5f8481D8F25d3966d2010DBf9B47fFbdf745A9E`.” - β€œIf an agent pays me 250 USDC, how much EUR lands in my bank after AsterPay's fee?” - β€œWhat are the current crypto market rates from AsterPay?” - β€œResolve the AsterPay demo merchant (business_id_type: demo) and show its IBAN details.” ## Privacy & data The connector is stateless and collects no personal data: it forwards only the parameters you supply for a single request to AsterPay's public API and returns the result. It does not read your chat history, memory, or files. Full details are in the [Privacy Policy](/privacy/) (section 13) and [Terms](/terms/). ## Support Questions about the connector: [petteri@asterpay.io](mailto:petteri@asterpay.io). General API documentation: [asterpay.io/docs](/docs/). Β© 2026 AELIRA LTD Β· AsterPay [Docs](/docs/) [Privacy](/privacy/) [Terms](/terms/) [Security](/security/) --- # Connect AsterPay to your agent in one line β€” Integrations Source: Markdown mirror: > Drop AsterPay into your agent in one line. MCP server, Python SDK, or direct HTTP. Free read endpoints, no signup, no API key. [AsterPay](/new/) [Check your site](/new/) [Get started](https://app.asterpay.io/signup) Integrations # Connect AsterPay in one line. Drop AsterPay into any agent: an MCP server, a Python SDK, or a plain HTTP call. Free read endpoints (trust score, settlement estimate) need no signup and no API key. Time to first paid call: under 10 minutes. From $0.001 /call Β· no minimums EUR in your bank in 10s Agent-native Β· KYA + ERC-8004 + x402/MPP ## Your first call Estimate a USDC to EUR settlement. No auth required for read endpoints. Pick your language. cURL Python JavaScript MCP Copy ``` # Free read endpoint, no API key β€” estimate 100 USDC β†’ EUR curl "https://x402.asterpay.io/v1/settlement/estimate?amount=100" ``` Copy ``` from asterpay import AsterPay client = AsterPay() # no key needed for read endpoints quote = client.settlement.estimate(amount_usdc=100) print(quote) # netEurAmount, eurRate, fees, estimatedSepaTime ``` Copy ``` const res = await fetch( "https://x402.asterpay.io/v1/settlement/estimate?amount=100" ); const { data } = await res.json(); console.log(data.netEurAmount, data.estimatedSepaTime); ``` Copy ``` // Add the AsterPay MCP server to any MCP-capable agent { "mcpServers": { "asterpay": { "command": "npx", "args": ["-y", "@asterpay/mcp-server"], "env": { "ASTERPAY_BASE_URL": "https://x402.asterpay.io" } } } } ``` Paid endpoints accept either `x402` or `MPP` payment proofs on the same call. Same surface, two protocols. ## Use it in your agent The MCP server exposes AsterPay's commerce tools (settlement estimate, KYA trust score, market data, merchant discovery, agent payments) to any MCP client. No API key. CC Claude Code One command, then restart Copy claude mcp add asterpay -- npx -y @asterpay/mcp-server Cu Cursor Add to `~/.cursor/mcp.json` Copy { "mcpServers": { "asterpay": { "command": "npx", "args": ["-y","@asterpay/mcp-server"] } } } CD Claude Desktop Add to `claude_desktop_config.json` Copy { "mcpServers": { "asterpay": { "command": "npx", "args": ["-y","@asterpay/mcp-server"] } } } Cx Codex / Windsurf / any MCP client Same stdio server Copy npx -y @asterpay/mcp-server DF DeerFlow Remote MCP β€” add to `extensions_config.json` Copy { "mcpServers": { "asterpay": { "enabled": true, "type": "http", "url": "https://mcp-api.asterpay.io/mcp" } } } ClawHub (OpenClaw) ships AsterPay as a bundled connector. DeerFlow agents get KYA trust score, merchant resolve, and USDCβ†’EUR settlement estimate via the remote MCP server β€” source at [github.com/aelira-labs/deerflow-skill](https://github.com/aelira-labs/deerflow-skill). Building a host yourself? Point any MCP stdio client at `npx @asterpay/mcp-server`. ## Every surface Pick the integration that matches your stack. All hit the same facilitator. ### Python SDK For Python agents and backends. Typed client over the HTTP API. Copy pip install asterpay [View on PyPI β†’](https://pypi.org/project/asterpay/) ### MCP server For any LLM agent that speaks MCP. Commerce tools, no API key. Copy npx @asterpay/mcp-server [View on npm β†’](https://www.npmjs.com/package/@asterpay/mcp-server) ### Direct HTTP Any language. Free read endpoints, x402 or MPP for paid calls. Import the OpenAPI 3.1 spec or Postman collection to auto-generate a client. Copy curl "https://x402.asterpay.io/v1/settlement/estimate?amount=100" [OpenAPI 3.1 β†’](/openapi.json) [Postman β†’](/postman/asterpay.postman_collection.json) [API docs β†’](/docs/) ### Attest CLI EU AI Act readiness scan for your agent or API, from the terminal. Copy npx @asterpay/attest scan [View on npm β†’](https://www.npmjs.com/package/@asterpay/attest) x402 + MPP dual No signup for reads EUR settlement <10s KYA trust scoring ERC-8004 identity ## Ship your first paid agent call. [Get started β†’](https://app.asterpay.io/signup) [Read the docs](/docs/) [AsterPay](/new/) Financial infrastructure for the agentic economy. EU-native, EUR-native. Built for MiCA. ##### Product - [x402 facilitator](/#x402) - [KYA trust scoring](/#tiers) - [Pricing](/#pricing) - [Compare](/compare/) ##### Developers - [Integrations](/new/integrations/) - [Docs](/docs/) - [GitHub](https://github.com/aelira-labs) - [MCP server](https://www.npmjs.com/package/@asterpay/mcp-server) - [llms.txt](/llms.txt) ##### Company - [Learn hub](/learn/) - [Partners](/partners/) - [Trust Center](/trust/) - [Blog](/blog/) ##### Social - [@Asterpayment](https://x.com/Asterpayment) - [Telegram](https://t.me/petterixai) Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus [Privacy](/privacy/) [Terms](/terms/) [Security](/security/) [Trust Center](/trust/) Free read endpoints return public estimates and metadata. AsterPay is non-custodial and settles EUR through licensed EU SEPA partner rails. Built for MiCA; live payout requires KYB. AsterPay is not affiliated with Aster (ASTER) DEX; it has no native token and no presence on BNB Smart Chain. --- # Integrate β€” AsterPay Ecosystem Partner Program Source: Markdown mirror: > Join the AsterPay ecosystem: free listing, co-marketing, 0% settlement markup for 12 months. x402 + MPP dual protocol. EUR settlement via SEPA Instant. [AsterPay](/) [Product](/#product) [Integration](/#sdks) [Dashboard](https://app.asterpay.io) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Create Free Account](https://app.asterpay.io/signup) [Home](/) [Product](/#product) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Create Free Account](https://app.asterpay.io/signup) No program fee Β· Open to all # Get listed in the AsterPay ecosystem Ship an integration, get permanent visibility to every AI agent that discovers AsterPay. Your logo in our agent card, llms.txt, and ecosystem directory. [Apply now](#apply) [View ecosystem](/ecosystem/) 5 partners already listed. Every approved integration appears in `/.well-known/agent.json`, `llms.txt`, and the [ecosystem directory](/ecosystem/) β€” visible to every AI agent and developer. ## What you get Every benefit is free. No equity, no fees, no catch. πŸ” ### Agent discovery Listed in `agent.json` and `llms.txt` so AI agents see your integration in-network automatically. 🌐 ### Ecosystem page Permanent logo and description on [asterpay.io/ecosystem](/ecosystem/) β€” the public integration directory. πŸ’° ### 0% markup for 12 months Zero AsterPay settlement markup on qualifying volume for a full year. Standard rates apply after. πŸ“’ ### Co-marketing Joint announcements on X, blog, and ecosystem page when you hit integration milestones. ⚑ ### Priority channel Direct Slack or shared channel to AsterPay engineering. Fast support, no ticket queues. πŸ”‘ ### Early access First look at MPE expansions, multi-currency settlement, Attest cloud, and roadmap features. ## Who's already in Infrastructure and program integrations. These are ecosystem partners β€” not company co-founders. I InsumerAPI On-chain attestation D Drip Usage metering C Circle Alliance Stablecoin program O ClawHub (OpenClaw) Agent skill registry x x402 Bazaar (CDP) Marketplace listing I Invoica x402-native invoicing ## How it works Four steps from application to ecosystem listing. 1 ### Fill the form Company name, product URL, logo, and how you use x402 or agents. Takes under 2 minutes. 2 ### Quick review We review within a few business days. No committee, no board approval. 3 ### Go live Your integration goes on the ecosystem page, agent.json, and llms.txt. Agents see you in-network. 4 ### Announce together Joint post on X and blog. We amplify your integration to our audience. ## Apply to integrate Fill in your details below. We'll review and get back to you within a few business days. 🎁 ### Every approved partner gets β€” free, immediately These aren't "coming soon" promises. You get all of this the day your application is approved. πŸ›‘οΈ Free Attest EU AI Act scan of your codebase πŸ“Š KYA Trust Score report for your agent πŸ’Έ $500 free settlement volume at 0% fee 🏷️ "Verified by AsterPay" badge for your site πŸ€– Priority ranking in agent.json discovery Company name * Your name * Email * Product / website URL * Category Select a category... Identity & attestation Analytics & operations Infrastructure & programs Agent platform & distribution Protocol / standard Other X / Twitter handle How do you use x402, agents, or EU settlement? * Company logo πŸ“Ž Click to upload or drag and drop PNG, JPG, SVG, or WebP Β· max 5 MB I agree to AsterPay's [Terms of Service](/terms/) and [Privacy Policy](/privacy/). * Add me to the AsterPay ecosystem updates list (product launches, protocol news, partnership opportunities). Unsubscribe anytime. Submit application No fees. We'll never share your data. Commercial terms agreed separately. βœ“ ### Application received We'll review your submission and get back to you within a few business days. Check your email for confirmation. ## Agent API πŸ€– MCP-ready AI agents can submit partner applications programmatically. Feed this to your agent or call it from your MCP server. cURL Python Node.js MCP Tool Copy ``` # Submit a partner application via API curl -X POST https://asterpay.io/api/partner-apply \ -H "Content-Type: application/json" \ -d '{ "company": "Acme AI", "name": "Jane Doe", "email": "jane@acme.com", "url": "https://acme.com", "category": "agent-platform", "twitter": "@acme_ai", "use_case": "x402 agent payments for our AI marketplace" }' ``` Copy ``` import requests response = requests.post( "https://asterpay.io/api/partner-apply", json={ "company": "Acme AI", "name": "Jane Doe", "email": "jane@acme.com", "url": "https://acme.com", "category": "agent-platform", "twitter": "@acme_ai", "use_case": "x402 agent payments for our AI marketplace", }, ) print(response.json()) # {"ok": true} ``` Copy ``` const response = await fetch( "https://asterpay.io/api/partner-apply", { method: "POST", headers: { "Content-Type": "application/json" }, body: JSON.stringify({ company: "Acme AI", name: "Jane Doe", email: "jane@acme.com", url: "https://acme.com", category: "agent-platform", twitter: "@acme_ai", use_case: "x402 agent payments for our AI marketplace", }), } ); const data = await response.json(); console.log(data); // { ok: true } ``` Copy ``` // MCP tool descriptor β€” add to your agent's tool list // The agent fills in the fields and calls the tool { "name": "asterpay_partner_apply", "description": "Apply to join the AsterPay ecosystem partner program. Free listing, agent discovery, $500 settlement credit, EU AI Act scan.", "inputSchema": { "type": "object", "required": ["company", "name", "email", "url", "use_case"], "properties": { "company": { "type": "string", "description": "Company name" }, "name": { "type": "string", "description": "Contact person name" }, "email": { "type": "string", "description": "Contact email" }, "url": { "type": "string", "description": "Product / website URL" }, "category": { "type": "string", "enum": ["identity", "analytics", "infrastructure", "agent-platform", "protocol", "other"] }, "twitter": { "type": "string", "description": "X / Twitter handle" }, "use_case": { "type": "string", "description": "How you use x402, agents, or EU settlement" } } }, "endpoint": "POST https://asterpay.io/api/partner-apply" } ``` πŸ’‘ The same endpoint accepts both form submissions and JSON. Agents can register autonomously β€” no browser needed. Logo can be added later. ## Questions? Reach out directly β€” we're happy to chat before you apply. [samantha@asterpay.io](mailto:samantha@asterpay.io) [Telegram](https://t.me/asterpaycommunity) [AsterPay](/) [Docs](/docs/) [Ecosystem](/ecosystem/) [Integrate](/partners/) [Blog](/blog/) [Privacy](/privacy/) [Terms](/terms/) [𝕏 Twitter](https://x.com/Asterpayment) [Telegram](https://t.me/asterpaycommunity) Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus --- # Privacy Policy - AsterPay Source: Markdown mirror: > AsterPay Privacy Policy. Learn how we collect, use, and protect your data. [← Back to AsterPay](/) # Privacy Policy Last updated: April 19, 2026 Β· Version 2.0 AELIRA LTD ("AsterPay", "we", "our", "us") operates the AsterPay trust, discovery and EUR-settlement layer for AI agent commerce. This Privacy Policy describes the personal data we process and your rights under the EU General Data Protection Regulation (GDPR) and other applicable EU data-protection law. ## 1. Data controller AELIRA LTD , Reg. No. HE 490977, VAT CY60362013K, 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus β€” is the data controller for personal data processed in connection with AsterPay services. Contact: [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 2. Personal data we collect - Account & merchant data: name, business email, role, company name, VAT ID, registered address, dashboard credentials. - KYB / AML data: certificate of incorporation, UBO information (name, date of birth, nationality, ID document where required), director and PEP declarations, source-of-funds declarations. - KYA (Know Your Agent) data: agent identifiers (e.g. ERC-8004 ID), wallet addresses, behavioural signals, operator attestations, Trust Score components. - Sanctions screening data: screening verdicts and identifiers exchanged with our enterprise sanctions / AML screening provider against EU, UN, OFAC and HM Treasury lists. - Transaction & settlement data: transaction hashes, amounts, timestamps, source and destination wallet addresses, IBAN/BIC of beneficiary accounts, conversion rates, fee breakdowns, refund and chargeback records. - Travel Rule data (Reg. (EU) 2023/1113): for crypto-asset transfers at or above €1,000, originator and beneficiary information (name, address, account/wallet identifier, and where required date of birth or other unique identifier). - Verification of Payee (VoP, PSD2): beneficiary name and account identifiers used for IBAN/BIC matching. - Technical data: IP address, user agent, request headers, API key identifiers (hashed), error and rate-limit logs. - Communications: support tickets, partnership emails, scheduling data via cal.eu/asterpay. ## 3. Purposes & legal bases - Provision of services (Art. 6(1)(b) GDPR β€” contract): operating accounts, processing payments, computing Trust Score, executing EUR settlement. - Compliance with legal obligations (Art. 6(1)(c) GDPR): KYB, AML, sanctions screening, Travel Rule, VAT, MiCA-related record keeping, EU AI Act transparency. - Legitimate interests (Art. 6(1)(f) GDPR): fraud prevention, security monitoring, abuse detection, product analytics, partner due diligence. - Consent (Art. 6(1)(a) GDPR): marketing communications, non-essential cookies and any features explicitly described as opt-in. ## 4. Recipients & processors We share personal data only as needed: - Licensed European payment partners for SEPA Instant settlement, IBAN issuance and partner-bank custody; - Stablecoin issuers and on-chain infrastructure (e.g. Circle for USDC/EURC operations, Base / Ethereum and partner RPC providers); - Sanctions and AML screening provider for per-transaction screening verdicts; - KYB / identity verification provider for company verification and UBO checks; - Cloud and hosting providers (Cloudflare, Railway, Supabase) for application infrastructure, with EU data-residency options where available; - Authorities when required by law, court order or a competent regulator. All processors are bound by Art. 28 GDPR data-processing agreements. Public blockchain networks (Base, Ethereum, etc.) are not processors: information written on-chain is publicly visible and immutable. ## 5. International transfers Where personal data is transferred outside the European Economic Area, we rely on Standard Contractual Clauses (SCCs) or other approved transfer mechanisms under Chapter V GDPR. Any such transfer is subject to a transfer-impact assessment. ## 6. Retention - KYB and AML records: retained for the periods required by EU AML legislation (currently 5 years after end of business relationship, extendable to 10 years where mandated). - Transaction and settlement records: minimum 5 years. - Travel Rule data: as required by Reg. (EU) 2023/1113 and national implementing law. - KYA / Trust Score signals: rolling window aligned with operator data-retention requests, except where required for AML / fraud-prevention purposes. - Technical logs: rolling 90 days unless retained longer for security investigation. ## 7. Your rights Under the GDPR you have the right to: access, rectification, erasure (subject to retention obligations), restriction, data portability, objection to processing based on legitimate interests, and to withdraw consent. You may also lodge a complaint with the Cyprus data-protection supervisory authority (Office of the Commissioner for Personal Data Protection) or your local EU supervisory authority. To exercise your rights, contact [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 8. Security We apply technical and organisational measures appropriate to the risk, including: encryption in transit (TLS 1.2+) and at rest, hashed API keys, role-based access controls, Supabase row-level security, REVOKE-by-default policies on backend-only tables, audit logging, and security headers (CSP, HSTS) on all public surfaces. Security disclosures: see [/security/](/security/) and our [/.well-known/security.txt](/.well-known/security.txt). ## 9. Cookies We use only essential cookies to operate the website and dashboard, plus opt-in analytics where applicable. Cookie preferences can be controlled via your browser. We do not use third-party advertising trackers. ## 10. Children AsterPay is not intended for individuals under 18 years of age and does not knowingly process personal data of minors. ## 11. Automated decision-making Trust Score and tier assignment may, in part, rely on automated processing. Where an automated decision produces legal or similarly significant effects (for example, refusing a settlement), you have the right to obtain human review and to contest the decision by contacting [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 12. Changes We may update this Privacy Policy. Material changes will be announced at least 30 days in advance by email or dashboard notice and reflected by an updated "Last updated" date. ## 13. AI assistant connectors (Model Context Protocol) AsterPay operates a hosted, read-only remote MCP (Model Context Protocol) server at [mcp-api.asterpay.io](https://mcp-api.asterpay.io) so AI assistants such as Claude can call AsterPay's public data tools (KYA trust score, USDCβ†’EUR settlement estimate, crypto market rates, and merchant payment-endpoint resolution). This connector's data practices are deliberately minimal: - No authentication and no accounts: the connector is unauthenticated. We do not issue credentials, create accounts, or identify the end user through it. - No personal data collected or stored: the server is stateless and read-only. It does not move money or hold funds. It forwards only the parameters the assistant supplies for a single request (a public wallet/agent address, a numeric amount, or a business identifier) to AsterPay's public API and returns the result. We do not persist these inputs, build user profiles, or retain conversation data. - No access to assistant data: the connector does not read the assistant's memory, chat history, conversation summaries, or user files. - Third-party sharing: none beyond the request reaching AsterPay's own first-party API (`x402.asterpay.io`). Wallet/agent addresses submitted for a trust check may be screened against public sanctions lists as described in sections 2 and 4. - Retention: request inputs are not retained by the connector. Standard technical logs (section 6) apply on a rolling 90-day window for security. - Transport security: HTTPS/TLS only. Connector questions: [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 14. Contact Privacy questions and rights requests: [petteri@asterpay.io](mailto:petteri@asterpay.io) Partnerships & onboarding: [samantha@asterpay.io](mailto:samantha@asterpay.io) --- # AsterPay Radar β€” AI search visibility that turns into euros Source: Markdown mirror: > See where your brand appears in ChatGPT, Gemini, Perplexity & Google AI β€” your share of voice, competitors and citations. Then make agents able to pay you in EUR. Weekly tracking from €29/mo. [AsterPay Radar](https://asterpay.io/) [How it works](#how) [Payability](#payable) [Pricing](#pricing) [Get free report](#top) ● AI search visibility + agent payability # See where AI mentions you β€” then make agents pay you AsterPay Radar tracks how ChatGPT, Gemini, Perplexity & Google AI see and cite your brand every week β€” and it's the only one that also makes AI agents able to pay you in EUR. Get free report β†’ 2 minutes Β· no signup Β· public data only Tracks ChatGPT Β· Gemini Β· Perplexity Β· Google AI Overviews Agent Commerce Readiness Β· yourbrand.com Live Β· updated weekly AI Visibility 38 /100 β–² 12% wk Citations 89 β–² 8% Agent-payable No 0 agents paid Share of voice over time yourbrand (you) Rival A Rival B Rival C Competitors Β· share of voice | | Brand | Visibility | Sent. | Pay | 1 Rival A | | 78% | No | 2 Rival B | | 71% | No | 3 yourbrand YOU | | 91% | EUR βœ“ | 4 Rival C | | 74% | No Top cited domains reddit.com Social 16.8% Β· 168 g2.com Reviews 14.2% Β· 142 techradar.com Article 8.5% Β· 85 ## Visibility is half the story. Can agents actually pay you? Every other AI-visibility tool stops at "are you mentioned". Radar closes the loop: we check whether an AI agent can discover, trust and pay your business β€” and we settle it as real euros in your bank. No other tracker turns a citation into cash. [Start tracking β€” €29/mo β†’](#pricing) 1 Seen. Tracked weekly across ChatGPT, Gemini, Perplexity & Google AI. ↓ 2 Trusted. KYA + sanctions screening so agents can transact with you safely. ↓ 3 Paid. x402 + MPP endpoints β€” agents pay per call or per order. ↓ 4 Settled. USDC/EURC β†’ EUR to your IBAN via SEPA Instant, under 10s. ## How Radar works From "invisible to AI" to "agent-payable" β€” tracked every week. 01 ### We ask the real prompts Radar runs the buyer questions your customers ask AI, across every major model. 02 ### You get a score & gaps Share of voice vs competitors, citations, sentiment, and your agent-payability score. 03 ### We track it weekly Snapshots over time + alerts when you move, a rival overtakes you, or a citation drops. 04 ### We make you payable Apply the fix-pack and connect EUR settlement so agents that find you can pay you. ## Simple weekly tracking. One price. Start free. Upgrade when you want weekly history, competitors and alerts. STARTER €29 /mo For one brand that wants to stay visible to AI. - βœ“ 1 domain, weekly tracking - βœ“ All 4 AI models - βœ“ Visibility score + citations history - βœ“ Agent-payability score [Start with a free report](#top) Most popular GROWTH €79 /mo For brands fighting for share of voice in AI answers. - βœ“ Up to 5 domains - βœ“ Competitor share-of-voice tracking - βœ“ Email + Slack alerts on changes - βœ“ Recommendations to close gaps - βœ“ EUR settlement ready [Start free, then €79/mo β†’](#top) AGENCY €199 /mo For agencies tracking many client brands. - βœ“ 25 domains + multi-client dashboard - βœ“ White-label reports - βœ“ Read API access - βœ“ Priority support [Talk to us](mailto:petteri@asterpay.io?subject=AsterPay%20Radar%20Agency) AsterPay Radar Β· AELIRA LTD Β· Cyprus [asterpay.io](https://asterpay.io/) Β· [Free tools](https://asterpay.io/tools/) Β· [Contact](mailto:petteri@asterpay.io) --- # Security - AsterPay Source: Markdown mirror: > AsterPay Security - Non-custodial architecture, internal security reviews, responsible disclosure and incident response. [AsterPay](/) [Sign in](https://app.asterpay.io/login) [Check my site](/new/) Trust & Security # Security Non-custodial by design. We never hold your funds, and every paying agent is screened. Last updated: July 5, 2026 Non-custodial architecture AsterPay is non-custodial payment infrastructure. We never take custody of funds: agent payments settle wallet-to-wallet on-chain, and crypto-to-EUR conversion and bank payout run on licensed European partner rails. ## Architecture security ### Non-custodial Private keys never touch our servers. On-chain payments settle directly between wallets. ### Licensed partner rails Stablecoinβ†’EUR conversion and SEPA Instant payouts to your IBAN are executed by licensed EU partners after KYB. ### Multi-chain support Secure integration with Base, Ethereum, Polygon, Arbitrum, and Optimism. ### Webhook signing HMAC-SHA256 signature verification for all webhook deliveries. ### API authentication The public API is keyless: free reads need no auth, and paid calls authenticate by payment (x402 / MPP). API keys are optional, for dashboard usage tracking and merchant features, with optional IP whitelisting for enterprise customers. ### Rate limiting Automatic rate limiting to prevent abuse and DDoS attacks. ## Audit status ### Smart contract exposure Non-custodial AsterPay does not deploy or operate its own fund-custody smart contracts. Payments settle through audited, industry-standard primitives (USDC / EIP-3009 `transferWithAuthorization` on Base, the ERC-8004 identity registry, EAS attestations) and licensed EU partner rails. Our own application code is covered by internal code reviews and the security reviews below; AsterPay never takes custody of user funds on-chain. ### Penetration testing In progress Our application code is covered by continuous internal security reviews. An independent third-party penetration test is planned; we will publish the provider, scope and date once it is completed. ### Infrastructure security - HTTPS only: All API endpoints use TLS 1.3 encryption - Database encryption: All sensitive data encrypted at rest - Secrets management: API keys and credentials stored securely - Regular updates: Dependencies updated regularly for security patches ## Threat model ### What we protect against - API key theft: Rate limiting, IP whitelisting, key rotation - Man-in-the-middle: TLS 1.3 encryption, HSTS - DDoS attacks: Rate limiting, CDN protection, auto-scaling - Data breaches: Encryption at rest, minimal data collection - Smart contract risk: Non-custodial design, audited standard token contracts (USDC/EIP-3009), application-level code reviews ### What we don't protect against - Wallet compromise: You are responsible for your own wallet security - Blockchain network issues: We cannot control blockchain congestion or forks - User error: Sending funds to wrong addresses, phishing attacks ## Incident response ### Security contact If you discover a security vulnerability, please contact us immediately: - Email: [petteri@asterpay.io](mailto:petteri@asterpay.io) - Response SLA: 24 hours acknowledgment - Please include: Description, steps to reproduce, potential impact ### Disclosure policy - We will acknowledge receipt within 24 hours - We will provide regular updates on remediation progress - We will credit researchers in our security advisories - We follow responsible disclosure practices ## Compliance & certifications ### GDPR & data protection EU data residency on the settlement path. Minimal PII retained; agent payment proofs are cryptographic, not identity-bearing. ### SOC 2 Type II In preparation SOC 2-aligned controls are implemented and operational across our infrastructure. An independent SOC 2 Type II attestation has not yet been completed. ### MiCA-aligned partner routing Compliant Crypto-to-fiat settlement is routed through MiCA-aligned licensed European payment partners. AsterPay operates as a technical service provider behind partner authorisations. ## Best practices for users ### API key security - Never commit API keys to version control - Use environment variables for API keys - Rotate keys regularly - Use IP whitelisting for production keys - Monitor API usage for suspicious activity ### Wallet security - Use hardware wallets for large amounts - Never share your private keys - Verify wallet addresses before sending funds - Keep wallet software updated - Use multi-signature wallets for teams ## Questions? For security-related questions: [petteri@asterpay.io](mailto:petteri@asterpay.io) ## Related documents - [Terms of Service](/terms/) - [Privacy Policy](/privacy/) [AsterPay](/) Financial infrastructure for the agentic economy. EU-native, EUR-native. Built for MiCA. ##### Product - [x402 facilitator](/#x402) - [ClinPay](/clinpay/) - [KYA trust scoring](/#tiers) - [Compare](/compare/) ##### Developers - [Integrations](/new/integrations/) - [Docs](/docs/) - [GitHub](https://github.com/aelira-labs) - [agent.json](/.well-known/agent.json) - [llms.txt](/llms.txt) ##### Company - [Learn hub](/learn/) - [Ecosystem](/ecosystem/) - [Partners](/partners/) - [Trust Center](/trust/) - [Blog](/blog/) ##### Social - [@Asterpayment](https://x.com/Asterpayment) - [Telegram](https://t.me/petterixai) Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus [Privacy](/privacy/) [Terms](/terms/) [Security](/security/) [Trust Center](/trust/) --- # AsterPay Service Level Agreement Source: Markdown mirror: > AsterPay availability targets, settlement timing, support response times, and incident severity definitions for enterprise agreements. [AsterPay](/) [← asterpay.io](/) Service Level Agreement # Reliability you can build on. Version 1.0 Β· Effective 19 June 2026 These are AsterPay's standard service-level objectives (SLOs). Contractual SLAs with financial service credits are available as part of an enterprise agreement. Free read endpoints and pay-per-call usage are provided on a best-effort basis under these same targets, without credits. To discuss an enterprise SLA, contact [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 1. API availability Target monthly availability for the production API (`api.asterpay.io` / `x402.asterpay.io`): | | Tier | Monthly availability target | Max downtime / month | Enterprise (contracted) | 99.9% | ~43 minutes | Standard / pay-per-call | 99.5% target (best-effort) | ~3.6 hours Availability is measured against the `GET /health` endpoint, excluding scheduled maintenance and the exclusions in section 6. Live component status is on the [status page](/status/). ## 2. EUR settlement timing Once a payment is confirmed and the recipient passes compliance checks, settlement is initiated over SEPA Instant. | | Metric | Target | SEPA Instant settlement (typical) | Funds in beneficiary account in seconds (often <10s) | Settlement initiation after confirmation | < 60 seconds | Fallback (beneficiary bank not SEPA-Instant reachable) | Standard SEPA, next business day Settlement is executed through licensed EU partner rails. Timing depends on the beneficiary bank's reachability and is outside AsterPay's direct control once funds leave the partner; the targets above describe the AsterPay-controlled portion. ## 3. Support response times | | Severity | Description | Target first response | Sev 1 β€” Critical | Production API down or settlement halted; no workaround. | 1 hour (24/7, enterprise) | Sev 2 β€” High | Major feature degraded or partial outage; workaround exists. | 4 business hours | Sev 3 β€” Normal | Minor issue, question, or non-blocking bug. | 1 business day Enterprise support, general enquiries and security reports: [petteri@asterpay.io](mailto:petteri@asterpay.io). ## 4. Incident communication During a Sev 1 or Sev 2 incident we post and update status on the [status page](/status/) and notify contracted enterprise customers directly. A root-cause summary is shared after Sev 1 resolution. ## 5. Scheduled maintenance Maintenance that may cause downtime is announced at least 48 hours in advance where practical and scheduled in low-traffic windows. Maintenance windows do not count against availability targets. ## 6. Exclusions - Factors outside AsterPay's control: upstream chain congestion or reorgs, beneficiary bank availability, third-party facilitators (Coinbase CDP), DNS/CDN provider incidents, and force majeure. - Misuse, traffic exceeding published rate limits, or use that violates the [Terms](/terms/). - Beta/preview features and endpoints explicitly marked as such. ## 7. Service credits For contracted enterprise customers, if monthly availability falls below the committed target, service credits apply per the terms of the signed agreement. Credits are the exclusive remedy for missed availability targets and must be requested within 30 days. Β© 2026 AELIRA LTD (HE 490977) Β· 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus Β· [Status](/status/) Β· [Terms](/terms/) --- # AsterPay Status Source: Markdown mirror: > Live operational status for the AsterPay API, EUR settlement, and x402 facilitator. Checked in your browser against the live health endpoints. [AsterPay](/) [← asterpay.io](/) # System status Checking… Live check runs in your browser. ## API api.asterpay.io Β· facilitator, KYA, market data Checking… ## EUR settlement USDC β†’ EUR estimate & SEPA Instant rail Checking… ## Agent discovery x402 / MPP discovery + .well-known Checking… This page probes the live endpoints from your browser each time it loads β€” the result reflects your network path too. Report an incident at [petteri@asterpay.io](mailto:petteri@asterpay.io). Enterprise availability targets are on the [SLA page](/sla/). Β© 2026 AELIRA LTD (HE 490977) Β· Cyprus Β· [asterpay.io](/) --- # AsterPay Subscriptions β€” Predictable pricing for unlimited agent traffic Source: Markdown mirror: > One flat monthly price covers every AI-agent payment AsterPay verifies and routes. You only pay 0.5% + €0.10 when we settle real euros to your bank. MiCA-aligned, Know Your Agent included. AsterPay [← Back to asterpay.io](/) AsterPay Subscriptions # Predictable pricing for unlimited agent traffic. One flat monthly price covers every AI-agent payment we verify and route for you. You only pay 0.5% + €0.10 when AsterPay settles real euros into your bank. As agent traffic grows, your processing cost stays flat. MiCA-aligned Β· Know Your Agent included ## Why merchants switch to a subscription Per-call pricing is fair when volume is small. Once AI agents start hammering your endpoints, it stops being predictable. πŸ“ˆ ### Costs that don't scale against you Agent traffic can 10x in a month. A flat subscription means your verification and routing bill doesn't move when it does. You forecast one number. πŸ›‘οΈ ### Every agent verified, no extra charge Know Your Agent trust scoring, sanctions screening and merchant discovery are included on every call. Block bad agents before they pay, at no per-check cost. πŸ‡ͺπŸ‡Ί ### Real euros, MiCA-aligned Agents pay in USDC/EURC over x402 or MPP; you receive EUR via SEPA Instant in under 10 seconds through a licensed European partner. Settlement billed only when money lands. ## What the flat fee covers The subscription buys the work with near-zero marginal cost. Settlement, which moves real money, stays usage-based and transparent. βœ“ Unlimited agent-payment verification & routing β€” x402 and MPP accepted on every endpoint, as many agent calls as you can drive. βœ“ Know Your Agent on every payment β€” ERC-8004 identity, Chainalysis/OFAC screening, 0–100 trust score, tiered spend limits. βœ“ Merchant Payment Endpoint discovery β€” agents resolve your verified payee details from provable sources. βœ“ EU AI Act Article 50 transparency β€” deterministic, rule-based decisions, fully disclosed and auditable. βœ“ EUR settlement at 0.5% + €0.10 per payout β€” this is the fiat off-ramp to your bank, not a crypto relay fee. USDC-to-USDC facilitators don't convert to euros. Billed only when money lands; minimum €0.50 per payout. ## Plans Start usage-based, move to a subscription the month it saves you money. EUR settlement is always 0.5% + €0.10 per payout on top, charged only when euros land. ### Pay as you go For early traffic and testing. €0 /mo - 0–100k agent calls / mo - €0.001 per call, no minimums - Know Your Agent included - No commitment, cancel anytime + 0.5% + €0.10 per EUR payout [Start free](https://app.asterpay.io/signup) MOST POPULAR ### Growth For stores and APIs with steady agent traffic. €299 /mo - Up to 1,000,000 agent calls / mo included - Extra calls €0.0008 each, never throttled - Pays for itself above ~300k calls / mo - Priority routing + KYA on every payment + 0.5% + €0.10 per EUR payout [Choose Growth](https://www.cal.eu/asterpay) ### Scale For high-volume marketplaces and platforms. €799 /mo - Up to 5,000,000 agent calls / mo included - Extra calls €0.0005 each - Dedicated routing & support - Custom trust-score policies + 0.5% + €0.10 per EUR payout (volume terms) [Talk to us](https://www.cal.eu/asterpay) Above 5M calls / mo, or need custom trust policies and volume settlement terms? [AsterPay Enterprise β†’](https://www.cal.eu/asterpay) Β· Minimum settlement fee €0.50 per payout; balances under €25 roll into your next SEPA Instant batch. ## The math, at your volume Drag to your monthly agent-call volume. Verification & routing only; EUR settlement (0.5% + €0.10/payout) is the same on every plan and excluded for a like-for-like comparison. Monthly agent calls 1,000,000 Pay as you go €1,000 Recommended: Growth €299 You save €701 / mo ## Turn unpredictable agent traffic into one predictable line item. Tell us your monthly agent-call volume and we'll show you the exact plan that pays for itself, with EUR settlement live in days. [Get your plan](https://www.cal.eu/asterpay) AsterPay is operated by AELIRA LTD (Cyprus). EUR settlement is executed via a licensed European payment partner under MiCA-aligned terms. Pricing shown is launch pricing and may change; fair-use limits apply to unlimited plans. --- # Terms of Service - AsterPay Source: Markdown mirror: > AsterPay Terms of Service. Please read these terms carefully before using our services. [← Back to AsterPay](/) # Terms of Service Last updated: April 19, 2026 Β· Version 2.0 These Terms of Service ("Terms") govern your access to and use of AsterPay, the trust, discovery and EUR settlement layer for AI agent commerce, operated by AELIRA LTD ("AsterPay", "we", "our", "us"). By accessing or using AsterPay, you ("User", "Merchant", "Developer", or "Agent Operator") agree to be bound by these Terms. ## 1. Description of Services AsterPay provides: - Trust layer (KYA β€” Know Your Agent): on-chain agent identity verification (ERC-8004), sanctions and AML screening via licensed providers, and a Trust Score (0–100) used to gate transaction limits. - Discovery layer (MPE β€” Merchant Payment Endpoint): resolves merchant identifiers (company name, VAT, domain) to verified IBAN/BIC and performs Verification of Payee (VoP, PSD2) checks. - EUR settlement layer: conversion of regulated stablecoins (USDC, EURC, EURCV) to EUR (and other supported EURs where available) via SEPA Instant and partner banking rails. Settlement is provided through licensed European payment partners; AsterPay does not custody funds beyond the time required to execute the conversion. - Payment protocol facilitation: dual-protocol facilitator support for the x402 protocol (HTTP 402, Coinbase open standard) and the Machine Payments Protocol (MPP, Stripe / Tempo open standard). Compatibility with Google AP2. - Developer infrastructure: APIs, SDKs, MCP servers, and the open-source Attest CLI (EU AI Act, Article 50) for integration and compliance tooling. ## 2. Eligibility & account types You must: - Be at least 18 years old and have the legal capacity to enter into contracts; - Not be located in, or a national of, any jurisdiction subject to comprehensive sanctions (including but not limited to those administered by the EU, UN, OFAC, or HM Treasury); - Not appear on any sanctions, PEP-with-restriction, or terrorism-financing list applicable in the European Union; - Provide accurate, complete and current information at registration and on request. Merchant accounts that wish to receive EUR settlement must complete KYB (Know Your Business) verification, including UBO disclosure and PEP declaration, before any EUR payout is enabled. ## 3. Fees Our published fee structure as of the date above: - Developer / agent API access: $0.01 USDC per call via x402 or MPP. Sandbox is free up to 1,000 calls per day. No monthly minimum, no signup fee. - Merchant EUR settlement β€” EU rail (default for EU-incorporated entities): 0.5% + €0.10 per settled transaction, all-in. No setup fee, no monthly minimum. Volume discounts available from €50,000 / month. - Merchant EUR settlement β€” US rail (US-incorporated entities, routed via US-licensed banking partner): 1.5% + €1.00 per settled transaction, all-in. The higher fee covers currency spread and SEPA passthrough at the US-licensed banking partner. - Enterprise & platform tier: negotiated pricing for transaction volumes above €500,000 / month, white-label, or multi-tenant configurations. Includes SLA and dedicated support. - Rail assignment: the applicable rail (EU or US) is determined by the merchant's country of incorporation at KYB onboarding and disclosed in writing before activation. Merchants are never silently moved between rails. - Network fees: third-party blockchain (gas) and SEPA Instant fees are passed through at cost where applicable; AsterPay does not mark them up. Fees may be updated at any time on at least 30 days' prior written notice (email or dashboard notification). Continued use after the effective date constitutes acceptance of the new fees. ## 4. Trust tiers and transaction limits Agent transactions are gated by Trust Score tier. Current published limits: - Open (score 0–20): max $1 per call, $50 per month. - Verified (20–50): max $100 per call, $5,000 per month. - Trusted (50–80): max $2,500 per call, $100,000 per month. - Enterprise (80–100): negotiated limits, available from Q3 2026. AsterPay reserves the right to refuse, hold, escrow, reverse, or refund any transaction at its discretion where Trust Score data, sanctions screening, or our risk-monitoring systems indicate a credible risk of fraud, sanctions exposure, money laundering or terrorism financing. ## 5. Acceptable use You may not use AsterPay, directly or via an agent acting on your behalf, for: - Activities prohibited by EU, US, UN or other applicable sanctions, anti-money-laundering (AML) or counter-terrorism-financing (CTF) law; - Fraud, identity misrepresentation, or facilitation of unauthorized payments; - Unlicensed gambling, regulated investment products without proper authorization, weapons trafficking, controlled substances, child sexual abuse material, or other content prohibited by EU law; - Circumventing Trust Score, KYA or KYB controls, including operating multiple agents to fragment transactions below screening thresholds (structuring); - Re-selling or sublicensing AsterPay APIs without a written reseller / platform agreement. ## 6. Compliance & regulatory framework AsterPay operates in the European Union under the laws of the Republic of Cyprus. - MiCA (Markets in Crypto-Assets): AsterPay is MiCA-aligned and provides regulated services through licensed European payment and crypto-asset partners. We do not hold a CASP licence; we operate as a technical service provider behind licensed European partners. - Travel Rule (Regulation (EU) 2023/1113): originator and beneficiary information is collected, transmitted and stored for crypto-asset transfers at or above €1,000. - VAT: European VAT is charged where applicable; reverse-charge applied to qualifying B2B EU customers. - EU AI Act, Article 50: AsterPay's published transparency information includes the Attest scan (open source) for integrators relying on agentic flows. - Sanctions screening: performed via an enterprise screening provider against EU, UN, OFAC and HM Treasury lists. Screening verdicts are stored for the periods required by applicable law. ## 7. Agent identity & KYA Where an AI agent transacts via AsterPay we may collect, process and store: the agent's on-chain identifier (ERC-8004 ID), wallet addresses, behavioural and reputation signals, and operator KYB attestations. This data is used to compute Trust Score, support fraud monitoring, and meet regulatory obligations. KYA data is treated as personal or operator data depending on context and is processed under our [Privacy Policy](/privacy/). ## 8. Non-custodial settlement AsterPay does not custody user funds for longer than the period required to execute conversion and settlement. Funds in transit may be held briefly at licensed European payment partners under partner-bank custody agreements. AsterPay is not a deposit-taking institution. ## 9. Risks You acknowledge that: - Blockchain transactions are irreversible; - SEPA Instant settlement is generally completed within seconds but may be delayed by partner-bank or beneficiary-bank issues outside our control; - Stablecoin issuers can pause, blacklist, or otherwise restrict transfers under their own terms; - Trust Score, KYA and screening signals reduce but do not eliminate fraud, sanctions, or counterparty risk. ## 10. Limitation of liability To the maximum extent permitted by law, AsterPay's total liability for any claim arising from or relating to these Terms or the services is limited to the fees paid by you to AsterPay in the twelve (12) months preceding the event giving rise to the claim. AsterPay is not liable for indirect, incidental, special, consequential or punitive damages. ## 11. Indemnification You agree to indemnify and hold harmless AsterPay, its affiliates, partners and personnel against any third-party claim, regulatory action, fine or cost arising from (a) your breach of these Terms, (b) your use of AsterPay in violation of applicable law, or (c) the conduct of any agent operating under your account. ## 12. Suspension & termination We may suspend, restrict or terminate access where we have reason to believe a user has breached these Terms, applicable law, partner-bank or stablecoin-issuer rules, or where required by a competent authority. Where lawful and operationally feasible, we will provide notice. Pending settlements may be returned to source or held in escrow pending investigation. ## 13. Modifications We may amend these Terms from time to time. Material changes will be notified at least 30 days in advance by email or dashboard banner. Continued use after the effective date constitutes acceptance. ## 14. Governing law & dispute resolution These Terms are governed by the laws of the Republic of Cyprus, without regard to its conflict-of-law provisions. EU consumer-protection mandatory rights are not affected. Any dispute shall be submitted to the competent courts of Nicosia, Cyprus, save where mandatory EU law confers jurisdiction elsewhere. ### Company information Legal entity: AELIRA LTD (Reg. No. HE 490977) Registered address: 9 Karpenisiou, Strovolos, 2021 Nicosia, Cyprus Jurisdiction: European Union (Cyprus) General contact: [petteri@asterpay.io](mailto:petteri@asterpay.io) Partnerships & onboarding: [samantha@asterpay.io](mailto:samantha@asterpay.io) ## 15. Contact For questions about these Terms, contact us at [petteri@asterpay.io](mailto:petteri@asterpay.io). --- # AI Crawlability Checker β€” AsterPay Source: Markdown mirror: > Check in seconds whether AI agents and LLMs can discover, read and act on your website. Free, no signup. By AsterPay. [AsterPay](https://asterpay.io/) [All tools β†’](https://asterpay.io/tools/) # AI crawlability checker See in seconds whether AI agents and LLMs can discover, read and act on your site β€” agent.json, llms.txt, machine-readable catalog, API and payment endpoint. Free, nothing stored. Check 0 checking This checks crawlability. The full report checks payability. AsterPay's Agent Commerce Readiness report runs real buyer prompts across ChatGPT, Gemini & Perplexity, shows your share-of-voice vs competitors, and whether an agent can actually pay you in euros. [Run my full report β†’](https://asterpay.io/agent-report/) Need an llms.txt? Use the free [llms.txt generator β†’](https://asterpay.io/tools/llms-txt/) --- # Free AI Visibility Tools β€” AsterPay Source: Markdown mirror: > Free tools to check and improve how AI agents see your business: AI crawlability checker, llms.txt generator, and the Agent Commerce Readiness report. [AsterPay](https://asterpay.io/) [← asterpay.io](https://asterpay.io/) # Free AI visibility tools Check and improve how AI agents and LLMs discover, understand and pay your business. No signup, nothing stored. [Flagship Β· free ## Agent Commerce Readiness report Real buyer prompts across ChatGPT, Gemini & Perplexity: your share-of-voice, competitors, citations β€” and whether an agent can pay you in euros. Run my report β†’](https://asterpay.io/agent-report/) [Free check ## AI crawlability checker In seconds: can AI agents discover and read your site? agent.json, llms.txt, catalog, API and payment endpoint. Check my site β†’](https://asterpay.io/tools/crawlability/) [Free generator ## llms.txt generator Generate a clean llms.txt so LLMs describe and cite your site correctly. Copy it to your site root. Generate llms.txt β†’](https://asterpay.io/tools/llms-txt/) --- # Free llms.txt Generator β€” AsterPay Source: Markdown mirror: > Generate a clean llms.txt file so AI agents and LLMs can understand and cite your site. Free, no signup. By AsterPay. [AsterPay](https://asterpay.io/) [All tools β†’](https://asterpay.io/tools/) # Free llms.txt generator An `llms.txt` file tells AI assistants what your site is, what matters, and where to look β€” so they describe and cite you correctly. Fill the form, copy the file to your site root at `/llms.txt`. ## Your site Site / brand name Homepage URL One-line summary Longer description (optional) Key pages β€” one per line as `Label | URL | short note` Contact email (optional) ## Generated llms.txt ``` # Your site ``` Copy Download llms.txt Place the file at https://yourdomain.com/llms.txt (site root). Many AI crawlers check this path. Is your site actually payable by AI agents? llms.txt helps agents understand you. AsterPay's free Agent Commerce Readiness report shows whether an AI agent can find, trust AND pay you in euros β€” across ChatGPT, Gemini and Perplexity. [Run my free report β†’](https://asterpay.io/agent-report/) --- # Treasury Agent β€” EUR ready when bills are due | AsterPay Source: Markdown mirror: > Live in production. Sign one mandate. The agent converts your USDC to EUR on schedule and lands it in your treasury IBAN via SEPA Instant β€” so you always have euros ready when bills are due. [AsterPay](/) [Home](/) [Docs](/docs/) [Learn](/learn/) [Contact](/#contact) Available now Β· Live on Base mainnet # Sign once. Agent pays. One mandate. Scheduled USDC β†’ EUR conversions. Delivered to your IBAN via SEPA Instant β€” before bills are due. [Apply for access β†’](https://app.asterpay.io/signup) [Talk to founder β†’](https://www.cal.eu/asterpay) EU-incorporated entities. KYB required before Treasury Agent unlocks in your dashboard. Live in production Β· Mandate flow on Base mainnet Β· SEPA Instant via licensed EU partners Not ready to apply? Get product updates by email. Notify me β†’ 50 seconds Β· Rent, payroll, utilities, taxes β€” all paid, all in your books. Click the demo to enable sound. ## How it works Four steps from signature to euros in your own treasury account. 01 / RULES ### Set the mandate Your treasury IBAN as the destination, a per-reload cap, a time window and a maximum frequency. Verified by PSD2 VoP that you own the account. 02 / SIGN ### Sign once One on-chain signature from your Safe smart account authorizes the agent's session key. No private keys leave you. 03 / EXECUTE ### Agent runs When a reload is due, the agent calls the payment operator with mandate-bounded parameters. Anything outside is rejected on-chain. 04 / SETTLE ### EUR in your account USDC converts to EUR via licensed CASP partners and lands in your own treasury IBAN via SEPA Instant. Pay rent, payroll, suppliers or taxes from there as you normally would. ## Why mandate-based Autonomous execution on rails you can audit, with custody you never give up. ### βœ“ Non-custodial by design USDC stays in your Safe smart account. The agent's session key is scoped to one operator contract and the mandate's parameters. AsterPay never holds your stablecoin balance. ### βœ“ Cryptographic guardrails Every execution carries the mandate hash. Off-rule payments revert on-chain before SEPA is touched. Revocation is one transaction from your Safe. ### βœ“ Locked destination IBAN Your treasury IBAN is verified by PSD2 Verification of Payee at onboarding and locked into the mandate. EUR can only ever land in your own account β€” never to a third party. Changing it requires signing a new mandate. ### βœ“ Full audit trail Each execution emits an EAS attestation with the mandate id, on-chain hash, EUR amount and SEPA reference. ERC-8004 is the open standard for verifiable agent identity β€” our Treasury Agent is registered as `#16850` on Base mainnet and can be verified by anyone [on-chain](https://basescan.org/address/0x8004A169FB4a3325136EB29fA0ceB6D2e539a432). ## Built for AI-native treasuries Not a B2C consumer wallet. Built for teams that hold stablecoins and have recurring fiat obligations. Web3 startups ### Stablecoin payroll & vendors Pay EU contractors, SaaS subscriptions and office rent in EUR β€” funded from your USDC treasury β€” without manual off-ramps every month. DAOs & foundations ### On-chain budget, off-chain delivery Convert multisig-approved USDC tranches to EUR on a schedule that matches grant payouts and operating expenses. Every reload carries the proposal id and on-chain receipt. Asset / property managers ### Recurring rent, utilities & tax outflows Pre-authorize a monthly EUR reload from your USDC reserves. Pay rent, utilities, payroll and tax from your own bank exactly when each is due β€” without scrambling for a manual off-ramp. ## Open standards, no lock-in Every layer is a public spec. Swap any component, keep the rest. `Safe` Smart account custody `ERC-8004` Agent identity `EIP-712` Mandate signature `SEPA Instant` EUR settlement rail ## Frequently asked The questions that come up first when teams evaluate handing payment authority to an agent. Does the agent move my money without my approval? No. The agent only executes reloads that fit a mandate you signed: your registered treasury IBAN as the destination, a per-reload cap, a time window and a maximum frequency. Any execution outside those rules is rejected on-chain and never reaches the EUR rail. Where do my euros end up? EUR lands in your own treasury bank account via SEPA Instant. The destination IBAN is locked to the one you registered when you signed the mandate and cannot be changed without signing a new mandate. You then pay rent, payroll, suppliers or taxes from your own bank as you normally would β€” the agent only handles the USDC-to-EUR reload. What custody model is this? Non-custodial. Your USDC sits in a Safe smart account that you own. The Treasury Agent has a scoped session key that can only call the payment operator with mandate-bounded parameters. AsterPay never holds your stablecoin balance. Can I cancel a mandate? Yes, instantly. Revoking a mandate is a single on-chain transaction from your Safe. Future executions are blocked the moment the revocation lands. You can also pause execution from the dashboard without revoking. Is this regulated? AsterPay operates EU-native through a regulated EU payment institution partner for SEPA settlement. AsterPay operates as a technical service provider behind licensed European payment and crypto-asset partners. Treasury Agent is offered to EU-incorporated entities first. Full audit trail per execution, ERC-8004 agent identity (`#16850` on Base mainnet) and EU AI Act Article 50 transparency are built in. What does it cost? 0.5% + €0.10 per settled EUR transaction. No subscription, no setup fee, no FX markup. Volume discounts start at €50k/month settled EUR volume per entity . Same pricing as the standard AsterPay EUR settlement rail. What if the agent has a bug or is compromised? The agent's session key is mathematically scoped to one operator contract and the parameters of your active mandate. A buggy or compromised agent cannot move funds outside the per-reload cap, your registered treasury IBAN, the time window or the frequency cap. EUR can never be diverted to a third-party account because the destination IBAN is locked into the mandate. A single on-chain transaction from your Safe revokes the agent's authority instantly β€” no support ticket required. Which chains and stablecoins are supported? Today: USDC on Base mainnet , with EUR settlement via SEPA Instant. EURC on Base for euro-denominated treasuries. Roadmap: Ethereum mainnet and Polygon are next targets in 2026; Solana under evaluation. Additional chains and stablecoins driven by customer demand. Has the smart contract been audited? The Treasury Agent is built on Safe β€” the most-audited smart account stack in production, securing $100B+ in assets. The mandate operator and session-key scoping contracts are pre-audit (independent audit scheduled before raising operator caps). On-chain code and ERC-8004 agent registration (`#16850`) are public on Base mainnet. How is GDPR and data residency handled? AsterPay processes settlement and customer data on EU infrastructure under GDPR. Beneficiary IBANs and KYB documentation are stored in EU regions only and are accessible only to AsterPay and the licensed payment partner for the duration required by EU AML rules. No customer data is shared with third parties outside the settlement chain. What is the SEPA Instant SLA if the partner rail goes down? SEPA Instant is offered with the partner's standard banking SLA (typically 99.9% monthly). If the instant rail is unavailable, payments fall back to standard SEPA same-day . Mandate execution is paused on-chain when the rail is degraded so no payment is initiated without a confirmable settlement path. ## Part of the AsterPay infrastructure Treasury Agent is one product in a stack of agent-payment infrastructure. Use them independently or together. Settlement layer ### AsterPay x402 USDC β†’ EUR settlement for AI agent commerce, x402 protocol native. [asterpay.io β†’](/) Trust layer ### Probe Independent audit and trust scores for AI agents and MCP servers. [getprobe.xyz β†’](https://getprobe.xyz) Identity layer ### AgentReady Open library for ERC-8004 agent registration and verifiable identity. [github.com β†’](https://github.com/aelira-labs/agent-ready) ## Sign your first mandate today. Apply for access in two minutes. Once your KYB is approved, the Treasury Agent unlocks in your dashboard and you can sign mandates, set rules and start paying in EUR. [Apply for access β†’](https://app.asterpay.io/signup) [Talk to founder β†’](https://www.cal.eu/asterpay) Or drop your email and we'll reach out: samantha@asterpay.io Β© 2026 AELIRA LTD Β· Cyprus Β· [asterpay.io](/) [Privacy](/privacy/) [Terms](/terms/) [Contact](/#contact) [@Asterpayment](https://twitter.com/Asterpayment) --- # tripwire β€” the payments senior your AI agent doesn't have Source: Markdown mirror: > A free, MIT ruleset that stops AI coding agents from double-charging customers, logging card numbers, and shipping payment code that trusts the client. 16 agent adapters. Built by AsterPay. [AsterPay](https://asterpay.io/) [← asterpay.io](https://asterpay.io/) Free Β· MIT Β· no dependencies # Your AI agent will double-charge your customers. tripwire is the senior who won't let it. LLM coding agents are confidently wrong about money: floats for currency, no idempotency keys, fulfilment on a redirect, logged card numbers, IDOR on payouts. tripwire is a copy-paste ruleset that stops agents at the seven ways they silently lose other people's money. [Get it on GitHub β†’](https://github.com/petteri74dev/tripwire) [Install in your agent](#install) 16 agent adapters Measured: 87% fewer money bugs No telemetry Built by AsterPay ## The seven tripwires Before writing or editing code that moves, stores, or reports money, the agent stops at every tripwire that holds, fixes it in the same change, and says which one fired. 1 ### Integer minor units + currency Money is `{ amount_minor, currency }` β€” never float, never a bare number. Float drift becomes real losses. 2 ### Idempotent money mutations Every charge, refund, transfer, and payout carries an idempotency key; a retry returns the first result. Retries double-charge without it. 3 ### Verify, then act Fulfil only after server-side verification of a webhook signature or on-chain tx. A spoofed "paid=true" hands out goods for free. 4 ### No secrets, PANs, or keys No card number, CVV, API secret, or private key in source, logs, or commits. One logged PAN is a breach. 5 ### Authorize the money path Confirm the caller owns the account before reading balances or moving funds. An unchecked id drains another user's money. 6 ### Explicit, auditable state Model and persist payment transitions with an audit trail; handle duplicate and out-of-order events. Silent state loss = an unreconcilable ledger. 7 ### No implicit FX or rounding Never mix currencies in arithmetic. Convert at an explicit boundary with a recorded rate, round once. Hidden rounding becomes a systematic skim. ## Install in your agent One file per agent, all generated from the same canonical ruleset β€” no per-agent tuning. ``` # Clone the ruleset git clone https://github.com/petteri74dev/tripwire # Cursor: copy harnesses/cursor/tripwire.mdc -> .cursor/rules/ # Claude Code: copy harnesses/claude-code/CLAUDE.md -> repo root # Codex / Amp: copy harnesses/codex/AGENTS.md -> repo root # Any agent: paste RULES.md into the system prompt ``` Cursor Claude Code Codex Windsurf Cline Aider GitHub Copilot Continue Zed Gemini CLI Amp Cody Roo Code Kilo Code OpenHands + generic prompt ## Prove it β€” measured, not vibes We sent 7 realistic money-code tasks to 2 models (gpt-4o, gpt-4o-mini) twice each: once with a neutral system prompt, once with tripwire loaded. 42 generations per side, scored by deterministic graders. 30 money-safety violations without the ruleset 4 with tripwire loaded 87% fewer, measured on real model output Not a clean zero β€” gpt-4o still slipped on logging and FX a few times even with the rules, and we report it as measured. Reproduce with your own key: `node benchmarks/agent-run.js`; every generation is saved for audit. A separate grader-validation run (`node benchmarks/run.js`) confirms the instrument detects all 7 failure modes (15 β†’ 0 on fixtures). [See the full results and honesty note β†’](https://github.com/petteri74dev/tripwire/blob/main/benchmarks/AGENT-RESULTS.md) ## Building agent commerce? tripwire keeps agent-written money code safe. AsterPay is the layer underneath it: KYA trust scoring, x402/MPP rails, and USDC to EUR settlement so agents can pay and get paid safely. [AsterPay is the trust + settlement layer β†’ asterpay.io](https://asterpay.io/) [github.com/petteri74dev/tripwire](https://github.com/petteri74dev/tripwire) Β· MIT Β© 2026 AELIRA LTD (AsterPay) Β· [asterpay.io](https://asterpay.io/) --- # Trust Center β€” AsterPay Source: Markdown mirror: > AsterPay Trust Center: entity and licensing, compliance and sanctions screening, security posture, settlement partners, and open attestations for the EUR settlement layer for AI agent commerce. [AsterPay](/) [Docs](/docs) [Security](/security) [API](/api) [Contact](#contact) Trust Center # Proof, not promises.The receipts behind every settlement. The single source of truth for AsterPay's entity, licensing model, compliance controls, security posture, and the open attestations anyone can verify on-chain. Operational MiCA-aligned ERC-8004 #16850 Sanctions screening live EU-native 99.9 % Settlement uptime Rolling 90-day <10 s Median settlement time USDC β†’ EUR via SEPA Instant 100 % Counterparties screened Sanctions & high-risk lists 0 Customer funds held Non-custodial settlement ● Illustrative β€” live volume, settlement count and latency to be wired from the x402-api metrics endpoint. AsterPay does not publish fabricated figures. 01 / Identity ## Entity & licensing Who we are, where we are regulated, and exactly how money moves. Operating entity AELIRA LTD Verified Jurisdiction Cyprus (EU) Β· Reg. HE 490977 Verified Registered address 9 Karpenisiou, Strovolos 2021, Nicosia, CY Verified Regulatory model Settlement & trust orchestration via licensed EU CASP / EMI partners Partner-backed Customer fund custody Non-custodial β€” funds never pooled by AsterPay Confirmed 02 / Controls ## Compliance & screening Every payment path is screened, scored, and built to EU expectations. ### πŸ›‘ Sanctions screening Every inbound counterparty wallet is screened against sanctions and high-risk lists before settlement. Hits are blocked, not flagged-and-forwarded. Coverage // OFAC, EU, UN lists ### β˜… KYA Trust Score Open 0–100 trust framework scoring agent wallets across seven components: wallet age, activity, sanctions, ERC-8004 identity, operator KYB, history, trust bond. Schema // /.well-known/kya-schema-v1 ### βš– MiCA alignment Settlement runs through licensed European payment partners. AsterPay's controls are built to MiCA and EU AML expectations for agent-initiated flows. Posture // MiCA-aligned ### πŸ“ Merchant onboarding Business onboarding (KYB) via Sumsub. Completed once at the merchant level β€” no per-transaction KYC on the agent payment path. Provider // Sumsub ### βœ‰ Travel Rule readiness Counterparty and originator data captured to support EU Travel Rule obligations on settlement legs handled by our regulated partners. Status // Partner-handled ### πŸ”’ Data protection EU data residency on the settlement path. Minimal PII retained; agent payment proofs are cryptographic, not identity-bearing. Framework // GDPR 02 / Accountability ## Who controls this agent? Crypto proves which wallet an agent is. KYA also resolves the human or legal entity behind it β€” in four verifiable layers, fail-closed. 1 Β· Wallet self-proof The agent signs every payment with its own key (EIP-3009 / EIP-191) Cryptographic 2 Β· On-chain owner ERC-8004 `ownerOf` resolves the registered owner of the agent identity On-chain 3 Β· KYC attestation Optional Coinbase KYC attestation for the wallet, read via EAS β€” pass/fail only, no PII EAS attested 4 Β· Operator binding Wallet bound to a KYB-verified legal operator via a signed challenge (EIP-191, SIWE-inspired β€” not EIP-4361) Live ### πŸ”— Verify it yourself The controller resolution for any agent wallet is a public, free read. No login, no PII β€” just the operator binding, its KYB status and jurisdiction. Endpoint // GET x402.asterpay.io/v1/agent/binding/{address} [See a live bound example β†’](https://x402.asterpay.io/v1/agent/binding/0xfccb9237bf6ccc4369bfca260854ad4fa71300f2) ● Non-custodial & honest by design β€” AsterPay stores operator metadata and KYB status only, never raw KYB documents. The binding is an EIP-191 `personal_sign` proof (EOA and EIP-1271 smart accounts), not an EIP-4361 sign-in. Legal name is shown only when KYB is approved. 03 / Hardening ## Security posture What is deployed today, and what is on the roadmap β€” stated honestly. Transport security TLS 1.3 Β· HSTS preload Deployed Content Security Policy Strict CSP on asterpay.io Deployed Security headers X-Frame-Options, X-Content-Type-Options, Referrer-Policy Deployed Vulnerability disclosure /.well-known/security.txt Published Error handling No stack traces or internals returned to clients Enforced Rate limiting Per-IP limits + automated scanner ban on production APIs Active SOC 2 Type II Controls mapping in progress In preparation 04 / Rails ## Settlement & rails How an agent payment becomes euros in a merchant bank account. ### ⇄ How a settlement works An agent pays in USDC, EURC or EURCV on Base, Polygon, Arbitrum, Optimism or Ethereum. AsterPay verifies the x402 / MPP payment proof, screens the counterparty, and our licensed CASP partner converts to EUR and pays the merchant bank account via SEPA Instant β€” typically in under ten seconds. Protocols // x402 (Coinbase) Β· MPP (Stripe/Tempo) ### 🌐 Rails & assets EUR via SEPA Instant today. GBP via Faster Payments and USD via ACH on the roadmap. Settlement assets: USDC, EURC, EURCV β€” with MiCA-native EUR stablecoins (e.g. EURAU) under evaluation as an additional EUR leg. Chains // Base, Polygon, Arbitrum, Optimism, Ethereum 05 / Verify ## Open attestations Trust you can check yourself. Every claim points to a public, verifiable source. [KYA Trust Score schema v1/.well-known/kya-schema-v1β†—](https://asterpay.io/.well-known/kya-schema-v1) [Security disclosure policy/.well-known/security.txtβ†—](https://asterpay.io/.well-known/security.txt) [x402 ecosystem listingx402.org/ecosystemβ†—](https://x402.org/ecosystem) [Open-source & librariesgithub.com/aelira-labsβ†—](https://github.com/aelira-labs) [ERC-8004 identity β€” Agent #16850Base Β· on-chain registryβ†—](#) [API & integration docsasterpay.io/docsβ†—](https://asterpay.io/docs) 06 / Get in touch ## Security, compliance & data requests Responsible disclosure, KYB/AML questions, GDPR requests β€” send it here and it reaches the founding team directly. Name Email * Topic Security / vulnerability disclosure Compliance / KYB / AML / sanctions Data protection / GDPR Partnership Other Message * Send message Β© 2026 AELIRA LTD Β· AsterPay Β· Cyprus HE 490977 AsterPay is operated by AELIRA LTD and provides settlement and trust orchestration through licensed European payment partners. AsterPay does not itself issue e-money or hold customer funds. "MiCA-aligned" describes our control posture and does not assert that AsterPay holds an EMT or CASP authorisation in its own name. Status indicators marked "in preparation" or "planned" are roadmap items, not current certifications. [Security](/security) Β· [Privacy](/privacy) Β· [Terms](/terms) --- # Try AsterPay β€” first call free, free EUR estimates, previews in every 402 Source: Markdown mirror: > Your agent [AsterPay](https://asterpay.io/) [← asterpay.io](https://asterpay.io/) No sign-up Β· no API key Β· live now # Your agent's first paid call is free. We removed every reason not to try the API. EUR settlement estimates are now free, every 402 shows you exactly what you'd get before you pay, and a brand-new wallet's first paid call is verified β€” but never charged. [Read the docs β†’](https://x402.asterpay.io/docs) [How first-call-free works](#first-free) x402 + MPP accepted USDC on Base + 4 chains EUR settlement via SEPA Instant ## Four changes, shipped July 4 We audited weeks of real agent traffic hitting our 402s and fixed the funnel instead of the marketing. FREE NOW ### EUR settlement estimate β€” $0 The single most-probed endpoint in our catalogue was paywalled for $0.005. That was backwards: the estimate is the shop window, the 0.5% settlement fee is the product. ``` GET https://x402.asterpay.io/v2/x402/offramp/estimate?amount=100 β†’ 200, no payment needed { "outputAmount": 91.83, "outputCurrency": "EUR", "estimatedDelivery": "10 seconds (SEPA Instant)" } ``` NEW ### First call free, per wallet Send a normally signed x402 payment. If your wallet has never paid AsterPay, we verify the signature, funding and nonce β€” then serve the response without settling . Your first call costs $0 and needs zero integration changes. One per wallet, endpoints up to $0.02, and the wallet must actually hold the USDC (that's the anti-farming gate). NEW ### See the goods before you pay Every 402 challenge now embeds an `example_response` β€” a truthful sample of the 200 body β€” so an agent can judge value before committing a single cent. ``` HTTP/1.1 402 Payment Required { "accepts": [...], "example_response": { "prices": { "BTC": 109432.5, ... } }, "first_call_free": { "eligible_endpoint": true, ... } } ``` NEW Β· $0.02 ### Agent-readiness scan, machine-callable The same scan that powers our homepage checker is now a paid x402 endpoint. Score any public site 0–100 on MCP, agent.json, llms.txt, OpenAPI and payability β€” from your own agent. ``` GET /v2/x402/agent-readiness?url=example.com β†’ 402 β†’ pay $0.02 β†’ { "score": 60, "bucket": "partial", "top_gaps": [{ "label": "Agents can't pay you yet" }] } ``` 60 SECONDS ### Try it right now Free endpoints need nothing. Paid endpoints return a 402 with everything your agent needs β€” and if it's your wallet's first time, the retry is free. ``` # 1. Free β€” EUR settlement estimate curl "https://x402.asterpay.io/v2/x402/offramp/estimate?amount=100" # 2. Paid β€” hit it once to see the 402 with example_response + first_call_free offer curl "https://x402.asterpay.io/v2/x402/crypto/prices" # 3. Pay (or claim your free first call) with the x402 SDK npm i @x402/fetch # or: pip install x402 ``` ## Then settle it in EUR Everything above is the funnel. The product: USDC in, EUR in a bank account via SEPA Instant in under 10 seconds, 0.5% + €0.10 per settlement, MiCA-aligned via licensed partner rails. [EUR settlement β†’ asterpay.io](https://asterpay.io/#settlement) [API docs](https://x402.asterpay.io/docs) Β· [Blog](https://asterpay.io/blog/) Β· [@Asterpayment](https://x.com/Asterpayment) Β· Β© 2026 AELIRA LTD (AsterPay) --- # AsterPay β€” Master Agent Skill Source: Markdown mirror: > Single-file install for Claude, Cursor, Codex, and any MCP-aware coding agent. # AsterPay β€” Master Agent Skill > Single-file install for Claude, Cursor, Codex, and any MCP-aware coding agent. > Trust check + first EUR settlement in one curl. **Operator:** AELIRA LTD (Cyprus, MiCA jurisdiction) **API base:** https://x402.asterpay.io **Site index:** https://asterpay.io/llms.txt **Full reference:** https://asterpay.io/llms-full.txt --- ## What AsterPay does AsterPay is the trust, discovery, and EUR settlement layer for AI agent payments. It accepts both **x402** (Coinbase HTTP 402) and **MPP** (Stripe/Tempo Machine Payments Protocol) on every paid endpoint, and converts USDC/EURC to EUR via SEPA Instant in under 10 seconds. Three product layers: 1. **TRUST (KYA β€” Know Your Agent)** β€” 5-layer trust score 0-100, sanctions screening (Chainalysis), ERC-8004 identity check. 2. **DISCOVERY (MPE β€” Merchant Payment Endpoint)** β€” agent passes a company name or VAT, AsterPay returns the IBAN/BIC with full validation and a disclosed verification method (bank-side PSD2 VoP via partner PSPs in rollout). 3. **SETTLEMENT** β€” USDC/EURC to EUR via SEPA Instant, MiCA-aligned via licensed partners. --- ## Install (pick one) ### MCP server (Claude Desktop, Cursor, Windsurf, Codex) ```json { "mcpServers": { "asterpay": { "command": "npx", "args": ["@asterpay/mcp-server"] } } } ``` 12 commerce tools, no API key, no signup. Boots in budget-only mode with zero config; orders settle on-chain via x402 (USDC on Base) when placed. ### Python SDK ```bash pip install asterpay ``` ```python from asterpay import AsterPay client = AsterPay() score = client.kya.score("0xAgentWallet...") print(f"Trust: {score['score']}/100 ({score['tier']})") ``` ### TypeScript SDK ```bash npm install @asterpay/sdk ``` ### Raw HTTP No SDK needed. Every free endpoint is `GET` and returns JSON. --- ## First call: trust check (FREE) ```bash curl https://x402.asterpay.io/v1/agent/trust-score/0x1234567890123456789012345678901234567890 ``` Returns: ```json { "success": true, "data": { "address": "0x1234...", "score": 72, "tier": "verified", "blocked": false, "components": { "identity": 85, "activity": 60, "credentials": 70, "behavioral": 75 }, "sanctions": { "clean": true, "provider": "chainalysis" } } } ``` Use this **before** any x402 payment over $1 to avoid paying sanctioned or blocked counterparties. --- ## First settlement quote (FREE) ```bash curl "https://x402.asterpay.io/v1/settlement/estimate?amount=100" ``` Returns the EUR amount, fee, exchange rate, and SEPA timing for a 100 USDC settlement. --- ## Resolve a merchant by company name (FREE) ```bash curl "https://x402.asterpay.io/v1/mpe/merchants/resolve?business_id=FI12345678&business_id_type=vat" ``` Returns the IBAN/BIC from AsterPay's merchant registry or the merchant's published payment manifest, with full IBAN validation and the verification method disclosed in the response (`vop_method`). --- ## Tool inventory (MCP server, 12 tools) `@asterpay/mcp-server` v2.1.0 is a commerce + budget server. All 12 tools work with no API key; placing an order settles on-chain via x402 (USDC on Base). KYA trust scoring, market data, and crypto analytics are available as HTTP endpoints (see above), not as MCP tools in this package. | Category | Tools | Cost | |----------|-------|------| | Budget | `set_budget`, `get_budget_status` | Free (no API key) | | Spending limits | `set_spending_limit`, `get_spending_summary` | Free | | Merchant discovery | `discover_merchants` | Free | | Products | `list_products`, `get_product`, `check_availability`, `get_business_info` | Free | | Orders | `place_order`, `get_order_status` | Free | | x402 payment | `get_x402_payment_details` | Free (order settles via x402) | --- ## Pricing summary - Free: KYA trust score, settlement estimate, MPE resolve, market rates, framework spec, agent card. - Paid per call: $0.001 to $0.10 USDC depending on endpoint, paid via x402 or MPP. - EUR settlement fee (EU rail): 0.5% + EUR 0.10 per settled txn. - EUR settlement fee (US rail): 1.5% + EUR 1.00 per settled txn. - No native AsterPay token. No token discounts. No subscription. --- ## Discovery URLs - Site index: https://asterpay.io/llms.txt - Full API reference: https://asterpay.io/llms-full.txt - Agent card (A2A/AP2): https://asterpay.io/.well-known/agent.json - x402 capability manifest: https://asterpay.io/.well-known/x402.json - KYA Trust Score schema v1: https://asterpay.io/.well-known/kya-schema-v1 - ChatGPT plugin manifest: https://asterpay.io/.well-known/ai-plugin.json - OpenAPI 3.1 spec: https://x402.asterpay.io/docs/json - Swagger UI: https://x402.asterpay.io/docs --- ## Compliance posture - MiCA jurisdiction. AELIRA LTD, Cyprus. - Sanctions screening on every paid call (Chainalysis). - Travel Rule applied above 1,000 EUR. - EU AI Act: KYA assessed as limited-risk, Article 50 transparency on every API response. - ERC-8004 Agent #16850 on Base mainnet. - x402 facilitator with a live capability manifest at https://asterpay.io/.well-known/x402.json - Member of Circle Alliance. --- ## Contact - Email: samantha@asterpay.io - X: @Asterpayment - Discord: linked from https://asterpay.io - Status: https://api.asterpay.io/v1/incidents/status