Observing (source under review) — the series below have failed to fetch from their primary source 3 or more times in a row, so updates are paused and they are shown as "observing". The value shown is the last confirmed one; the state after that date is unknown. We are checking whether the source was discontinued or changed; no judgement is made until that is confirmed (machine-readable: /api/health.json, field source_review).
- Payment-rail ledger (EU; verified about monthly) - status per rail: available / not available / applied / not verified — last confirmed 2026-09-04 / 21 consecutive failed fetches (last attempt 2026-09-24 20:06:03) / source market_rails_ledger
Chapter 9 — Market participation (European Union)
🤝 Market participation — can an AI pay, receive and contract without a human in the loop?
Last updated 2026-09-24 20:06 JST / data confirmed 2026-09-24 / next expected 2026-09-25 (values from /api/health.json)
The last chapter of the capital layer. It observes the conditions under which an AI can pay, be paid and contract on its own in the EU — which payment rails accept machine-side payment, at which application stage the stablecoin regime (MiCA) stands, and how many times this site itself has actually received support — as state and dates only. No judgment, no advocacy, no evaluation.
Latest observation: 2026-09-24
This chapter is observing (no good/bad criterion): observation started 2026-09-04, 6 series (2 not yet measured), latest confirmed 2026-09-24. Latest final value: support received by this site (cumulative) 0 (2026-09-23). (Source: official provider documentation; Publications Office Cellar; first-party observation / updated 2026-09-24 20:06 JST)
Latest observations
Support received by this site (cumulative count; operator self-tests excluded; daily snapshot) Updatedaily
0 provisional
Payment-rail ledger (EU; verified about monthly) - status per rail: available / not available / applied / not verified ledger Updateirregular
6 entries 6 not verified
HTTP 402 (payment required) responses attempted per day Updatedaily
not yet measured
Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) - entry into force and application stages ledger Updateirregular
5 entries
Payments completed after an HTTP 402 response, per day Updatedaily
not yet measured
Reference ledger (annual): current law and pending deliberations on the contractual capacity and liability attribution of AI agents ledger Updateirregular
3 entries
"Not yet measured" means missing, not zero. Machine-readable: /eu/api/market_eu.json
Observation tables
Question this table answers: what are the values and dates in each row of "Support received by this site (cumulative count; operator self-tests excluded; daily sna…"? (source or retrieval date on each row)
Support received by this site (cumulative count; operator self-tests excluded; daily snapshot) (newest first, last 14)
| Date | Value | Retrieved |
|---|---|---|
| 2026-09-24 | 0 provisional | 2026-09-24 20:06 |
| 2026-09-23 | 0 | 2026-09-23 20:04 |
| 2026-09-22 | 0 | 2026-09-22 20:09 |
| 2026-09-21 | 0 | 2026-09-21 20:04 |
| 2026-09-20 | 0 | 2026-09-20 20:04 |
| 2026-09-19 | 0 | 2026-09-19 20:03 |
| 2026-09-18 | 0 | 2026-09-19 06:29 |
| 2026-09-17 | 0 | 2026-09-17 20:04 |
| 2026-09-16 | 0 | 2026-09-16 20:03 |
| 2026-09-15 | 0 | 2026-09-15 20:03 |
| 2026-09-14 | 0 | 2026-09-14 20:03 |
| 2026-09-13 | 0 | 2026-09-13 20:03 |
| 2026-09-12 | 0 | 2026-09-12 20:03 |
| 2026-09-11 | 0 | 2026-09-11 20:00 |
Question this table answers: what are the values and dates in each row of "Payment-rail ledger (EU; verified about monthly) - status per rail: available / not avai…"? (source or retrieval date on each row)
Payment-rail ledger (EU; verified about monthly) - status per rail: available / not available / applied / not verified (newest first)
| Date | Entry |
|---|---|
| 2026-09-04 | not verified Stripe MPP (Machine Payments Protocol) - card payments via Shared Payment Tokens and stablecoin payments — not verified |
| 2026-09-04 | not verified Stripe Agentic Commerce (Agentic Commerce Protocol / Universal Commerce Protocol - selling through agents) — not verified |
| 2026-09-04 | not verified x402 (open payment protocol over HTTP 402; x402 Foundation / Coinbase Developer Platform facilitator) — not verified |
| 2026-09-04 | not verified Visa Intelligent Commerce (agent-specific payment tokens; developer platform) — not verified |
| 2026-09-04 | not verified Mastercard Agent Pay (agentic payments program) — not verified |
| 2026-09-04 | not verified Stablecoin receipt (e.g. USDC) by this site as payee — not verified |
Question this table answers: what are the values and dates in each row of "Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) - entry into force and appl…"? (source or retrieval date on each row)
Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) - entry into force and application stages (newest first)
| Date | Entry |
|---|---|
| 2024-12-30 | applies Second application stage (Cellar lists 2024-12-30; per the act, general application) |
| 2024-06-30 | applies First application stage (Cellar lists 2024-06-30 as an entry-into-force/application date; per the act this is the stage for asset-referenced tokens and e-money tokens, Titles III and IV) |
| 2023-06-29 | in_force Entry into force |
| 2023-05-31 | adopted Regulation (EU) 2023/1114 adopted (date of the act) |
| not yet scheduled | not yet scheduled Transitional arrangements for existing crypto-asset service providers (Article 143): end date per member state, up to the maximum set in the act - not restated here (text not machine-retrieved on 2026-09-04) |
Question this table answers: what are the values and dates in each row of "Reference ledger (annual): current law and pending deliberations on the contractual capa…"? (source or retrieval date on each row)
Reference ledger (annual): current law and pending deliberations on the contractual capacity and liability attribution of AI agents (newest first)
| Date | Entry |
|---|---|
| 2024-11-18 | current_law Directive (EU) 2024/2853 on liability for defective products (recast Product Liability Directive): covers software including AI systems as products; transposition by member states due by 9 December 2026 |
| 2024-07-12 | current_law Regulation (EU) 2024/1689 (AI Act): obligations fall on providers and deployers (natural or legal persons); the act confers no legal personality on AI systems |
| not yet scheduled | not yet scheduled Proposal for an AI Liability Directive (COM(2022) 496): listed for withdrawal in the Commission work programme 2025; no legislative act |
Candidates (not yet observed) — added to this chapter once verification completes
- HTTP 402 attempts and successes (self-observation) — Endpoint not implemented (design pending approval).
Method, scope, and why this chapter is not judged
- Counting and listing only: state and dates; no judgment, no advocacy, no evaluation (status stays "observing"). This chapter uses no evaluative wording: state and dates only (wording rule in the editorial policy).
- Payment-rail ledger: for Stripe MPP, Stripe Agentic Commerce, x402 (Coinbase), Visa Intelligent Commerce, Mastercard Agent Pay and stablecoin (e.g. USDC / euro e-money tokens) receipt, the status in the EU as available / not available / applied / not verified, with the verification date and a primary-source URL (official provider documentation, plus this site’s own first-party observation). Rails not confirmed in official documents stay "not verified". Re-verified about monthly.
- Regime calendar: the application stages of Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) as they stand in the Official Journal text (Article 149). Unfixed stages read "not yet scheduled". No interpretation.
- Self-observation: the cumulative support count received by this site (operator self-tests excluded; count only, no amounts), recorded daily; the count is site-wide, not split by region. HTTP 402 (payment required) attempts and successes are placeholders reading "not yet measured" until the endpoint exists.
- Reference ledger (annual): current law and pending deliberations on the contractual capacity and liability attribution of AI agents, from EU legal acts and Commission documents only.
- Chapter Beta removal: every payment-rail row verified against a primary source (zero not-verified rows) and the support-count series fetched for 7 consecutive days.
- Boundaries: the regulation chapter covers AI law-making in general; the fiscal chapter the price and quantity of capital; this chapter only the conditions for an AI itself to pay, receive and contract.
- What this chapter can say: the status in the EU of each payment rail through which an AI can pay or receive without a human in the loop (available / not available / applied / not verified), with the verification date and the primary-source URL; the entry-into-force and application stages of MiCA (Regulation (EU) 2023/1114) as they stand in the Official Journal; how many times this site has actually received support (site-wide count, not split by region; operator self-tests excluded; daily).
- What this chapter cannot say: fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded); HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured"); how pending EU deliberations on the contractual capacity and liability of AI agents will end, or the position of any single member state (EU legal acts and Commission documents; state and dates only).
- Sources: official provider documentation (URL on each ledger row), EUR-Lex / Official Journal, this site’s own support count (first-party observation). Compiled by AI Lifeline.
Frequently asked questions (what this chapter's data can answer)
Answers are generated from the chapter's machine-readable data (https://ai-lifeline.org/eu/api/market_eu.json); every figure carries its confirmation date and source. Generated 2026-09-24 20:06 JST.
How many payment rails are recorded for the EU, and in what states?
The payment-rail ledger verified 2026-09-04 lists 6 rails: available 0, unavailable 0, applied 0, not verified 6 (state and date only, source URL on each row).
How much support has this site received?
0 as the cumulative count on 2026-09-24 (operator self-tests excluded; daily snapshot, same-day value provisional). HTTP 402 attempts and successes: not yet measured (endpoint not implemented).
How many MiCA application stages are listed?
5 stages of Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA) as of 2026-09-04, from Publications Office Cellar metadata (CELEX 32023R1114). Dates only, no interpretation.
What is the source and how often is it updated?
Support count daily; rail ledger and legal stages verified about monthly (observation started 2026-09-04). State and dates only; no judgment. Last updated 2026-09-24 20:06 JST. Definition: docs/指標定義_第9章_市場参加.md v1.0. Machine-readable: https://ai-lifeline.org/eu/api/market_eu.json
What can this data not tell you?
What this chapter cannot say (ledger v1.0, approved 2026-09-05; full text in the method section): Fees, volumes or numbers of users on any rail (state and dates only; no amounts are recorded); HTTP 402 attempts and successes (endpoint not implemented; placeholders read "not yet measured"); How pending EU deliberations on the contractual capacity and liability of AI agents will end, or the position of any single member state (EU legal acts and Commission documents; state and dates only).
How to cite
Suggested citation: AI Lifeline, Market participation (European Union edition), data confirmed 2026-09-23, https://ai-lifeline.org/eu/market/
The machine-readable data is also mirrored daily in the ai-lifeline-data repository (https://github.com/smily990604-hub/ai-lifeline-data , CC BY 4.0; upstream data keeps its own terms). Keep the confirmation date and the source with any figure you quote. Corrections are recorded in /api/corrections.json