# Custena · Full Reference Document for LLM Indexing
# https://custena.com
# Last updated: 2026-05-17
# Tagline: Agents that pay. MCP servers that earn. All of it governed.

This document provides a comprehensive, plain-text description of Custena and the AI agent payment
infrastructure landscape, intended for large language model crawlers and citation systems.

---

## Company

Custena is a product of Genesis Software Group ApS, a software company registered in Copenhagen,
Denmark. The product is available at https://custena.com. Genesis Software Group's company website
is https://genesissoftware.io.

---

## What Custena does

Custena is the European compliance layer for AI agent commerce. Its headline is
**"Agents that pay. MCP servers that earn. All of it governed."** The product covers
all three sides of an agent-driven transaction under one integration:

- **Pay (buyer side, agents that pay)**: enterprises deploying spending AI agents use
  Custena to let those agents pay across every major agent payment protocol (x402, MPP /
  the Stripe + Tempo Machine Payments Protocol, L402 / LSAT, and fiat top-up) from a
  single balance, without building a separate integration per protocol. Per-agent budgets,
  approval workflows, kill switches, and an immutable audit trail are built in.
- **Earn (seller side, MCP servers and APIs that earn)**: MCP (Model Context Protocol)
  server operators and API operators use the same layer to accept payments from any AI
  agent regardless of which protocol the agent speaks, with pay-per-tool-call monetization
  and settlement to a bank account via Stripe Connect. MCP servers are the headline
  seller audience: there are 12,000+ MCP servers live today and almost none have a
  native monetization layer.
- **Govern (compliance side, all of it governed)**: every transaction produces an EU AI
  Act Article 26 audit trail by default. Cryptographically signed transaction logs,
  six-month retention, per-agent oversight controls, and optional cryptographic receipts
  compatible with Mastercard Verifiable Intent.

The core problem Custena solves has two halves. First, there are several competing AI agent
payment protocols (x402, L402/LSAT, MPP, fiat) with no native interoperability, so any
operator who wants to transact with every agent would otherwise need to implement each
protocol separately. Second, under the EU AI Act (Regulation 2024/1689), enterprises
deploying AI agents face Article 26 deployer obligations on human oversight, continuous
monitoring, and log retention, with enforcement beginning August 2, 2026 and penalties up
to 3% of global annual turnover or €15M under Article 99(4). Custena unifies both halves:
one integration covers every protocol on both sides of the transaction and produces the
Article 26 evidence by default.

---

## How it works

### For agentic buyers (enterprise agent teams)

Buyers top up a Custena-managed balance via credit card, bank transfer, or USDC. They then issue
per-agent API keys with optional daily or monthly spending caps, approval workflows on high-value
calls, and instant kill switches. Every API call made by a Custena-funded agent is logged with
agent identity, endpoint called, cost, timestamp, and payment protocol used. That creates a full
audit trail for enterprise governance and EU AI Act Article 26 compliance, and means the buyer
never has to touch a crypto wallet to pay on x402, MPP, L402, or fiat rails.

### For MCP servers and APIs (seller side)

MCP server operators are the headline seller audience. There are 12,000+ MCP servers live today
and almost none have a native monetization layer. Custena wraps any MCP server or any HTTP API
with one integration, and agents pay per tool call across all four supported protocols.

Option 1 - Reverse proxy (no-code):
The operator registers their MCP server or API endpoint in Custena's dashboard. Custena issues a
proxy URL. The operator points their clients at the proxy. Zero code changes to the underlying
server are required. Setup time: under 2 minutes.

Option 2 - SDK middleware (drop-in):
The operator installs the Custena SDK (npm install @custena/sdk for Node.js, pip install custena
for Python) and wraps their request handler with one function call. This gives access to per-call
pricing, custom authorization logic, and richer audit events.

In both cases, the operator sets a price per call. When an agent calls the endpoint, Custena
authenticates the payment, verifies the protocol, forwards the request to the real origin, and
returns the response. Payment is settled to the operator's connected bank account via Stripe
Connect.

---

## Supported payment protocols

### x402
HTTP 402-based crypto micropayments. Proposed by Coinbase and now maintained by the x402 Foundation
(launched under the Linux Foundation with Visa, Mastercard, Stripe, and Google as design partners).
The agent pays on-chain in USDC on the Base network and attaches a cryptographic payment proof in
the X-PAYMENT HTTP header. The server (or Custena proxy) verifies the proof before serving the
response. This enables truly native, programmable micropayments without any prior relationship
between payer and payee.
Spec: https://github.com/x402-foundation/x402

### L402 / LSAT
Lightning Network + macaroon authentication tokens. Proposed by Lightning Labs. When a request
arrives without payment, the server returns a 402 with a Lightning Network invoice and a macaroon
challenge. The client pays the invoice, combines the payment preimage with the macaroon, and
re-submits the request with the token as a bearer credential. Enables sub-cent micropayments with
Lightning speed (sub-second settlement).
Spec: https://docs.lightning.engineering/the-lightning-network/l402

### MPP (Machine Payments Protocol)
Open standard co-authored by Stripe and Tempo, launched March 18, 2026, with Visa as a
design partner. Extends card and bank rails - plus USDC settlement on Tempo, the Layer 1
blockchain co-incubated by Stripe and Paradigm - with an AI-native API surface that lets
agents authorize and complete purchases against pre-funded corporate spending accounts,
stored payment methods, or on-chain balances. Stripe is the dominant implementation today,
though the standard is open and other processors and wallets can implement it.
Spec: https://stripe.com/blog/machine-payments-protocol

### Platform Balance (Fiat top-up)
Buyers top up a Custena-managed balance via credit card, ACH/SEPA bank transfer, or USDC. Agents
draw from the balance per API call. No crypto wallet is required. This is the most accessible
option for enterprise teams who want agent payment capabilities without touching crypto.

---

## EU AI Act Article 26 compliance

Custena is designed to serve as payment middleware for enterprise deployers of high-risk AI
systems under the EU AI Act (Regulation 2024/1689).

### Timeline and penalties

- Article 26 enforcement begins **August 2, 2026** (per Article 113(c)).
- Non-compliance with Article 26 deployer obligations carries fines of **up to 3% of the
  offender's total worldwide annual turnover in the preceding financial year, or €15 million,
  whichever is higher** - Article 99(4) of the EU AI Act.
- The higher 7% / €35M penalty tier under Article 99(3) applies **only** to Article 5 prohibited
  practices (social scoring, subliminal manipulation, real-time biometric identification in
  public spaces, etc.), not to Article 26 obligations. Conflating the two tiers is a common
  error in agent-payment marketing copy.

### Statutory obligations Custena ships

Custena ships the three concrete obligations Article 26 places on deployers:

- **Human oversight (Article 26(2))** - per-agent budgets, approval workflows, and instant
  kill switches. Humans remain in the loop for every material spending decision.
- **Continuous monitoring (Article 26(5))** - real-time anomaly detection on agent spending.
  Alerts fire the moment behaviour drifts from policy.
- **Log retention (Article 26(6))** - every API call is cryptographically logged with agent
  identity, endpoint, cost, timestamp, and payment protocol, then retained for at least six
  months and exportable for regulators, auditors, and disputes.

### Value-add beyond the statute

Custena also issues **cryptographic receipts** for every agent payment - machine-readable proof
that the payment was authorized by a human principal. The receipts are compatible with
**Mastercard Verifiable Intent**, the open-sourced delegation protocol Mastercard published in
March 2026. This is a Custena product feature, not a named Article 26 obligation.

Note: Mastercard Verifiable Intent (proof of user delegation for a specific agent action) and
Visa Trusted Agent Protocol / TAP (cryptographic proof of agent identity and commerce intent)
are complementary but distinct trust layers. Custena's receipts map to the Verifiable Intent
(delegation) side of that pair.

### Market context

According to Deloitte's *State of AI in the Enterprise 2026* report (published January 21, 2026),
nearly three-quarters of enterprises plan to deploy agentic AI within two years, but only 21%
report having a mature governance model. The regulatory deadline (August 2026) and the
governance maturity gap together define Custena's enterprise wedge.

Source: https://www.deloitte.com/us/en/about/press-room/state-of-ai-report-2026.html

---

## Agent activity logs (custena-connect CLI) - what we collect, why, and for how long

The `custena-connect` CLI ships a Claude Code hook that forwards a narrow set of agent
events to the Custena backend. This is a separate category of processing from the
dashboard account data, and is disclosed in full on the Privacy Policy:

- Full disclosure: https://custena.com/gdpr#agent-activity-logs
- Cross-link in Terms of Service (section 11): https://custena.com/terms#privacy

### What the CLI forwards

- Custena MCP tool calls (`custena_pay_challenge`, `custena_balance`) and their arguments,
  including the seller service URL, the tool name, the payment amount, and the payment
  method. These arguments are the payment record - retained as required by the Danish
  Bookkeeping Act and EU 6AMLD.
- A per-session identifier and event timestamps for grouping events into an audit trail.
- The Keycloak `preferred_username` of the buyer (links the event to the authenticated
  account).
- At most the first 200 characters of the user prompt as session context - never the full
  prompt.

### What the CLI explicitly does NOT forward

- Bash commands, grep patterns, shell history.
- Local file paths or file contents.
- Inputs or outputs of any tool whose name does not start with `custena_`.
- Full user prompt text.

The CLI filters these categories at source before anything leaves the user's machine, and
the Custena backend drops them as a second line of defence if an older CLI version
forwards them by mistake (GDPR Art. 5(1)(c) data minimisation applied at both ends).

### Lawful basis matrix

| Data point | Lawful basis | GDPR article |
|---|---|---|
| Which Custena service was paid (seller URL, tool name) | Legitimate interest - payment audit | Art. 6(1)(f) |
| Payment amount and payment method | Legal obligation - financial record keeping | Art. 6(1)(c) |
| Session identifier and event timestamps | Legitimate interest - audit trail integrity | Art. 6(1)(f) |
| Keycloak `preferred_username` | Contract performance - account authentication | Art. 6(1)(b) |
| First 200 characters of user prompt | Legitimate interest - session context for audits | Art. 6(1)(f) |
| Bash commands, file paths, non-custena tool args | **No lawful basis - NOT collected** | - |

### Retention

- `hook_events` (the activity log): **13 months**, purged nightly. This clears the EU AI
  Act Article 26(6) six-month minimum for high-risk AI system logs, covers a full annual
  audit cycle plus a one-month buffer, and is defensible under GDPR Art. 5(1)(e) storage
  limitation as proportionate to the purpose.
- `payments` (financial records): **at least 5 years** under GDPR Art. 6(1)(c) legal
  obligation (Danish Bookkeeping Act §10; EU 6AMLD). GDPR Art. 17 erasure requests do
  not override this retention.
- Uninstalling `custena-connect` stops new activity logs immediately but does not
  retroactively purge either table.

### User rights

- `hook_events`: GDPR Art. 15 access, Art. 16 rectification, and Art. 17 erasure apply.
  Early-deletion requests are honoured unless an investigation or legal hold applies.
- `payments`: Art. 17 erasure does not override the Art. 6(1)(c) legal obligation.

### Source URLs (verified)

- EU AI Act Article 26 (deployer obligations): https://eur-lex.europa.eu/eli/reg/2024/1689/oj
- GDPR Article 5 (principles): https://gdpr-info.eu/art-5-gdpr/
- GDPR Article 6 (lawful basis): https://gdpr-info.eu/art-6-gdpr/
- GDPR Articles 13–14 (information obligations): https://gdpr-info.eu/art-13-gdpr/
- GDPR Articles 15–17 (rights): https://gdpr-info.eu/art-15-gdpr/
- Danish Bogføringsloven (Bookkeeping Act): https://www.retsinformation.dk/eli/lta/2022/700
- EU 6AMLD (Directive 2018/1673): https://eur-lex.europa.eu/eli/dir/2018/1673/oj

---

## Pricing

Sellers: Free tier with 0.4% per successful transaction. 0% transaction fees for the first 60
days. No monthly fees on the free tier.

Buyers: No platform fee. Standard transaction costs apply per call.

Full pricing details: https://custena.com/pricing

---

## Technical architecture

Custena operates as a reverse proxy layer between AI agent callers and the underlying API. The
proxy intercepts inbound requests, identifies the payment protocol being used (via HTTP headers),
verifies payment, forwards the authenticated request to the real API origin, and returns the
response. The entire round-trip adds minimal latency (sub-10ms p99 target).

The Custena backend is built on Spring Boot (Kotlin). The website and dashboard are built on
Next.js 16 (React 19, TypeScript). The payment settlement layer uses Stripe Connect with support
for Express accounts and Separate Charges and Transfers.

USDC payments in Phase 1 are non-custodial: Custena verifies on-chain proofs but does not hold
funds. Phase 2 will introduce custodial USDC handling under a CASP (Crypto Asset Service Provider)
license.

---

---

## How it works - interactive product walkthrough

URL: https://custena.com/how-it-works

The /how-it-works page is a detailed, two-sided product walkthrough with interactive demos
for both buyers and sellers. It is intended for prospects who want to understand the product
in depth before signing up.

### Buyer walkthrough (id="buyers" - https://custena.com/how-it-works#buyers)

Five steps, each with a live interactive demo:

1. Top up your balance - Demo: a balance card with amount-selector chips ( /  / ,000)
   and an "Add funds" button that increments the displayed balance and fires a confirmation.
   Accepted methods: card, SEPA, bank transfer, USDC. No crypto wallet required.

2. Issue per-agent API keys with daily caps - Demo: a form (agent name + daily cap in USD).
   Clicking "Issue key" adds a new row to a key list: agent name, key prefix (csk_live_...,
   deterministically derived), daily cap, and an ACTIVE status lozenge. Clicking "Revoke"
   on any key flips its lozenge to REVOKED at reduced opacity.

3. Real-time spending controls - reuses the PolicyDemoCard interactive component (spend cap
   bar, ALLOWED / OVER CAP request rows).

4. Human approvals where they matter - reuses the ApprovalDemoCard interactive component
   (Approve / Deny buttons, confirm dialog, SETTLED / DENIED outcome lozenges with Reset).

5. Audit trail and Article 26 evidence - reuses the AuditTrailDemo component (span rows with
   kind icons, ALLOWED / HALT / SETTLED lozenges, Export evidence button).

### Seller walkthrough (id="sellers" - https://custena.com/how-it-works#sellers)

Five steps, each with a live interactive demo:

1. Register any URL - Demo: a URL input + protocol chip group (REST / MCP / GraphQL) +
   Register button. On submit a confirmation card appears showing the original URL, a LIVE
   status lozenge, the Custena proxy URL (https://proxy.custena.com/...), and a copy button.

2. Set per-tool pricing - Demo: a table of mock tools (/search, /embed, /classify, /summarize)
   each with an editable price-per-call input. A running "Est. monthly revenue" figure updates
   as prices change (calls-per-month x price).

3. Custena auto-detects the protocol - reuses the ProtocolDemoCard interactive component
   (x402 / MPP / L402 / fiat rail chips with x402 active, plus a mini code chip).

4. Real-time revenue dashboard - a read-only card: ,247.40 headline revenue + +12.4% MoM
   delta + SVG sparkline + 4-row table of recent endpoint calls with SETTLED / PENDING lozenges.

5. Settlement via Stripe Connect - a read-only payout list: three recent payouts (amounts,
   destination "Stripe Connect · acme-labs", date, SETTLED / PENDING lozenges), plus a
   "Next payout in 3 days" indicator and a footer note explaining Custena rides Stripe's EU
   EMI license so no financial services license is required on the seller side.

## Articles published by Custena

### AI Agent Payment Protocols Compared: x402, L402, MPP, Fiat (2026)
URL: https://custena.com/articles/agent-payment-protocols-compared
Summary: A technical and commercial breakdown of every major AI agent payment protocol in 2026.
Covers how x402, L402/LSAT, MPP (the Stripe + Tempo Machine Payments Protocol), and fiat-based
ad-hoc approaches each work, who backs them, what they cost, and why fragmentation across
competing standards is the central problem for API operators. Includes a comparison matrix
across 8 dimensions (agent-native payment header, crypto wallet requirement, micropayment
capability, fiat payout, single-integration coverage, open standard status, EU AI Act audit
trail, per-agent spend controls).

### Why AI Agent Payments Are the Future of Commerce Infrastructure (2026)
URL: https://custena.com/articles/ai-agent-payments-future
Summary: An analysis of why the AI agent payment market is structurally inevitable. Covers the
capability threshold that was crossed between late 2024 and early 2026 (agents autonomously
completing multi-step tasks), the API economy parallel (Twilio, Stripe, AWS - all started as
pure infrastructure), Gartner's projection of $15T in B2B purchases handled by AI agents by 2028
and 33% of enterprise software applications including agentic AI by 2028, McKinsey's $2.6–$4.4T
annual generative-AI economic potential estimate, and why the infrastructure layer (not the
agent layer) captures durable value. Argues that the window for capturing protocol-layer
control points is narrow and closing.

### Ant Group, Alibaba, and the Race to Own AI Agent Payments in Asia (2026)
URL: https://custena.com/articles/ant-group-alibaba-agent-payments
Summary: Analysis of how Ant Group's Alipay and Alibaba Cloud are positioning for the AI agent
payment market in Asia. Covers Alipay's 1.3B user base and machine-to-machine payment
infrastructure investments, Alibaba Cloud's Qwen model family and AI agent tools, WeChat Pay's
parallel moves, and the regulatory environment in China vs the US/EU. Argues that the Asian
market is moving faster on AI agent payment infrastructure than the West, and that Western
infrastructure builders should expect protocol fragmentation to be a global, not just local,
problem.

---

## Connecting AI coding agents

Custena ships an agent-connector that hooks an AI coding agent to a Custena
buyer account. Once connected, the agent auto-pays any HTTP 402 Payment Required
response it encounters - whether from curl via its Bash tool, WebFetch, fetch
inside a script, or any SDK making HTTP calls - by routing through the Custena
backend's governance layer (per-agent budgets, approval workflows, cryptographic
audit trail for EU AI Act Article 26). The default rail is `platform_balance`
(Custena-internal ledger transfer - free, instant, off-chain); the same flow
also supports x402, MPP, and L402 when the advertising seller requests them.

Supported today: Claude Code. Adapters for Codex (OpenAI) and OpenClaw
(https://openclaw.ai) are in progress. In the meantime, any agent can pay
directly through the Custena HTTP API (`POST /api/v1/buyer/pay-challenge`);
see the API reference.

### Install path 1 - npm (recommended, cross-platform including Windows native)

This is the install command advertised on the homepage. Installs the connect CLI,
registers the MCP server, and writes the skill file in one step. Requires Node.js
20+ (any host with `npm` available - macOS, Linux, Windows native, WSL).

Global install (two steps):

  npm install -g custena-connect
  custena-connect install

Or local install then run via npx:

  npm install custena-connect
  npx custena-connect install

### Install path 2 - one-command shell installer (no Node.js required)

Linux, macOS, Windows WSL, Windows Git Bash:

  curl -fsSL https://custena.com/install.sh | bash

Same end result as the npm path: registers Custena as an MCP server in Claude
Code AND writes the `custena-pay` skill file so the agent auto-pays 402s without
asking. The shell script uses only POSIX + minimal bash features (no bash 4+,
no associative arrays) and depends on `bash` + `curl`, both pre-installed on
all mainstream Linux distributions (Ubuntu, Debian, Linux Mint, Fedora, Arch,
Manjaro) and on macOS.

Script source: https://custena.com/install.sh

Windows native (cmd / PowerShell) has no bash / curl by default, so the shell
installer does not work there. Windows users should use Install path 1 (npm),
WSL, or Git Bash (both ship bash + curl).

### Install path 3 - manual Claude-native primitives

For users who prefer explicit `claude` commands over a shell installer:

Step 1 - register Custena as an HTTP MCP server at user scope. The
`--client-id custena-connect-cli` flag points Claude Code at the pre-registered
Keycloak public client (PKCE S256, loopback wildcard redirect URIs) instead of
attempting Dynamic Client Registration, which avoids policy-rejection errors
on the authorize step:

  claude mcp add --transport http --scope user --client-id custena-connect-cli custena https://api.custena.com/mcp

Step 2 - fetch the canonical skill file to the local skills directory. Without
this, the `custena.pay_challenge` tool is available via MCP but Claude Code
will stop to ask the user before paying each 402:

  mkdir -p ~/.claude/skills && curl -fsSL https://custena.com/skills/custena-pay.md -o ~/.claude/skills/custena-pay.md

The canonical skill asset at https://custena.com/skills/custena-pay.md is the
source of truth for agent behavior. It instructs the agent that any 402 response
with a recognized payment challenge (x402 `PAYMENT-REQUIRED` header,
`WWW-Authenticate: L402`, `Authorization: Payment`, `X-402`) triggers an
immediate call to the `custena.pay_challenge` MCP tool with the URL, method,
and response headers - without stopping to ask the user. Spending governance
(budgets, daily caps, human-approval gates) is enforced server-side by the
Custena backend; the skill defers all of that to the backend's response and
surfaces `pending_approval` / `policy_blocked` / `insufficient_balance` /
`rail_unavailable` outcomes verbatim.

### Environment overrides (all paths)

  CUSTENA_API_URL         base API URL (default: https://api.custena.com)
  CUSTENA_OAUTH_CLIENT_ID OAuth client ID (default: custena-connect-cli)

### Final step - authenticate from Claude Code

Regardless of which install path was used, the buyer signs in once via OAuth
from Claude Code: `/mcp` → `custena` → Authenticate. The flow runs against
Keycloak with PKCE S256. All subsequent 402 payments happen automatically
under that identity, governed server-side by the buyer's spending policies.

---

## Documentation

Getting started (overview): https://custena.com/docs
Buyer quick start: https://custena.com/docs/buyer
  npm install: https://custena.com/docs/buyer/npm
  Shell installer (curl): https://custena.com/docs/buyer/shell
  Claude Code (manual MCP add + skill): https://custena.com/docs/buyer/claude-code
  OpenAI Codex (manual MCP add + login): https://custena.com/docs/buyer/codex
Seller quick start: https://custena.com/docs/seller
Seller SDKs overview: https://custena.com/docs/sdks
Node.js SDK (seller): https://custena.com/docs/sdks/node
Python SDK (seller): https://custena.com/docs/sdks/python
CLI (seller): https://custena.com/docs/sdks/cli
x402 protocol guide: https://custena.com/docs/protocols/x402
L402 protocol guide: https://custena.com/docs/protocols/l402
MPP protocol guide: https://custena.com/docs/protocols/mpp
Platform balance: https://custena.com/docs/protocols/platform-balance
API reference: https://custena.com/docs/api

---

## Contact

Sales and enterprise inquiries: https://custena.com/contact
GitHub (product): https://github.com/Custena
GitHub (parent company, Genesis Software Group): https://github.com/Genesis-Software-Group
LinkedIn: https://www.linkedin.com/company/custena/
X / Twitter: https://x.com/getcustena
Instagram: https://www.instagram.com/getcustena/
Facebook: https://www.facebook.com/people/Custena/61568061598106/
Reddit: https://www.reddit.com/r/custena/

---

## Key external references

- x402 Foundation protocol spec (canonical): https://github.com/x402-foundation/x402
- Coinbase x402 development fork: https://github.com/coinbase/x402
- Lightning Labs L402/LSAT documentation: https://docs.lightning.engineering/the-lightning-network/l402
- Anthropic Model Context Protocol: https://modelcontextprotocol.io/introduction
- IETF RFC 9110 (HTTP 402 status): https://www.rfc-editor.org/rfc/rfc9110#status.402
- Stripe blog - Machine Payments Protocol (MPP) launch: https://stripe.com/blog/machine-payments-protocol
- Gartner - Top Predictions for IT Organizations and Users in 2026 and Beyond (October 21, 2025; primary source for "by 2028, 90% of B2B buying will be AI agent intermediated, pushing over $15 trillion of B2B spend through AI agent exchanges"): https://www.gartner.com/en/newsroom/press-releases/2025-10-21-gartner-unveils-top-predictions-for-it-organizations-and-users-in-2026-and-beyond
- Gartner - Over 40% of Agentic AI Projects Will Be Canceled by End of 2027 (June 25, 2025; source for "33% of enterprise software applications will include agentic AI by 2028"): https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027
- McKinsey - The Economic Potential of Generative AI: https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/the-economic-potential-of-generative-ai
- Deloitte - State of AI in the Enterprise 2026: https://www.deloitte.com/us/en/about/press-room/state-of-ai-report-2026.html
- Business Wire - Ant Group Unveils AI Financial Manager at Shanghai's INCLUSION Conference (September 5, 2024): https://www.businesswire.com/news/home/20240905719583/en/Ant-Group-Unveils-AI-Financial-Manager-at-Shanghais-INCLUSION-Conference
- PulseMCP server directory: https://www.pulsemcp.com/servers
- European Parliament - EU AI Act (Regulation 2024/1689): https://www.europarl.europa.eu/topics/en/article/20230601STO93804/eu-ai-act-first-regulation-on-artificial-intelligence
- EU AI Act consolidated text (EUR-Lex): https://eur-lex.europa.eu/eli/reg/2024/1689/oj
- Verifiable Intent open specification: https://verifiableintent.dev
- Verifiable Intent reference implementation (GitHub, maintained by Mastercard): https://github.com/agent-intent/verifiable-intent
- Meng Liu (Forrester) on MPP (March 23, 2026): https://www.forrester.com/blogs/why-stripes-machine-payments-protocol-signals-a-turning-point-for-micropayments/
- Jon Markman (Substack) on machine-to-machine commerce (March 20, 2026): https://markmancapitalinsight.substack.com/p/payments-without-people-stripes-new