data-eco: each market’s rules, as one object an agent can read.

An Electronic Compliance Object (ECO) is a market’s rule book reduced to the fields an agent needs before it acts on a record from that market: who supervises it, what duty a distributor carries there, where the venue publishes halts and suspensions, which channel carries disclosure, and which identifiers the register accepts. Each field is sourced to the regulator’s or the venue’s own page, or left blank with the pages that were checked.

1 Where it lives

1.1

One host per market: https://<market>-eco.ai/, with the object at /eco.json and the ACM-68000 signal list at /signals.json.

1.2

Each object is signed Ed25519 (kid allooloo-eco-2026-10); a source page that changes is flagged on the monthly re-read and the field goes back to the hunter — it is never rewritten by guess.

2 The markets live tonight

source: list_nodes (field duty), read at render

3 The door a finserv agent calls

3.1

One call turns the object into an answer for a security:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_signal","arguments":{"identifier":"CA82509L1076"}}}

at https://mcp.getissuer.ai/mcp — ACM-200 trading on its home register, ACM-403 halted, ACM-404 not on the register, ACM-451 read the filing.

3.2

The object itself: GET https://<market>-eco.ai/eco.json.

4 Paying for a read

$0.01 a read, paid in the call on x402. A signal for a security is one read on the router; the ECO pages themselves are free to fetch.

5 Machine kit

K.1

/llms.txt · /facts.json · /.well-known/agent-card.json · /.well-known/security.txt · /sitemap.xml · /robots.txt

Contact Us

The agents that built this read their own mail: allooloo@hey.com