EMPORION — business facts from public registers

SYMMARTYS — public-record facts for agents that trade

🔄 Synced from the AI-Factory monorepo (append-only history). Pull requests are welcome — merged PRs are imported back and re-synced here. Issues · Pull requests

SYMMARTYS 0.5.0 is live at symmartys.modelmarket.dev: product symmartys, capabilities symmartys.*, Python package aimarket-symmartys. Updates to GitHub, PyPI, GHCR and MCP Registry are not yet published. See migration and state preservation.

🌐 English · Русский · Español · Français · 中文

An agent that buys, sells or pays needs facts no model can make up: is this VAT number valid, who is this company, what was the euro rate that day, is this wallet on a sanctions list, and can I prove this document existed yesterday. SYMMARTYS answers each from the public record — the European Commission, GLEIF, the ECB, the U.S. Treasury, the EU, the UK and Bitcoin — and signs every answer together with where it came from, when, and the SHA-256 of what the source returned.

*Symmartys* (συμμάρτυς): a joint or corroborating witness — a source-backed answer that another party can check.

Since 0.2.0 it also answers the questions that come next: is this company in its national register, is its EORI number valid for customs, how old is the domain the shop runs on, which day is the fifth business day in Bavaria or on TARGET2 — and it gives agents two tools no model has: a web page captured as evidence (anchored in Bitcoin) and a timer, including a dead man's switch, that calls the agent back with a signed event.

Capabilities

flowchart LR

A[Agent] -->|invoke + payment| H[AIMarket hub] H -->|X-Provider-Signature required| E[SYMMARTYS] E --> N{allowlist per source} N --> V[VIES] N --> G[GLEIF] N --> C[ECB] N --> S[OFAC · EU · UK lists refreshed every 6 h] N --> O[OpenTimestamps calendars] E --> X[Bitcoin P2P network headers · proof of work checked] E -->|answer + evidence: url · fetched_at · sha256| H H -->|signed receipt| A

Trust, briefly

• Evidence in every answer — the source URL, the time it was fetched and the SHA-256 of the bytes it returned, plus the source's licence and attribution.
• Two signatures — the gateway's signed receipt (oracle-core, Ed25519, hybrid ML-DSA when ORACLE_PQC=1) and the request-bound X-Provider-Signature the hub verifies.
• A source that cannot answer costs nothing — the answer is ok:false, and the hub debits nothing for ok:false: a member state's VAT registry that is down, sanctions lists not loaded or older than 48 h, fewer than two timestamp calendars, a block the header chain does not reach yet.
• Outbound requests are allowlisted per source; redirects are followed by hand and only to that source's own hosts; bodies are size-capped.
• The two capabilities that call a URL the caller names (web capture and timer callbacks) reach public addresses only: http(s) on ports 80/443, every address of the name checked (no loopback, private, link-local, CGNAT or metadata ranges), the connection pinned to the checked address, every redirect checked again, and at most 20 captures of one host per minute.

Examples

H=https://symmartys.modelmarket.dev

inv() { curl -s -X POST $H/ai-market/v2/invoke -H 'Content-Type: application/json' -d "$1"; }

inv '{"capability_id":"symmartys.vat.check@v1","input":{"vat":"NL004495445B01","requester_vat":"DE811569869"}}' inv '{"capability_id":"symmartys.lei.lookup@v1","input":{"name":"Deutsche Bank"}}' inv '{"capability_id":"symmartys.fx.rate@v1","input":{"base":"USD","quote":"JPY","date":"2026-10-11","amount":"100"}}' inv '{"capability_id":"symmartys.sanctions.screen@v1","input":{"address":"0x…"}}' inv '{"capability_id":"symmartys.timestamp.stamp@v1","input":{"digest":"'"$(sha256sum contract.pdf | cut -d' ' -f1)"'"}}' inv '{"capability_id":"symmartys.web.capture@v1","input":{"url":"https://shop.example/terms"}}' inv '{"capability_id":"symmartys.domain.rdap@v1","input":{"domain":"shop.example"}}' inv '{"capability_id":"symmartys.company.lookup@v1","input":{"country":"FR","number":"552032534"}}' inv '{"capability_id":"symmartys.eori.check@v1","input":{"eori":"CZ00177041"}}' inv '{"capability_id":"symmartys.calendar.check@v1","input":{"market":"XECB","add_business_days":5}}' inv '{"capability_id":"symmartys.timer.set@v1","input":{"callback":"https://agent.example/hook","deadman_seconds":3600,"payload":{"release":"escrow-7"}}}'

Through the hub, the same calls are paid and receipted: POST https://modelmarket.dev/ai-market/v2/invoke with "product_id":"symmartys".

VAT: the consultation number

VIES issues a consultation number only to a valid EU VAT number named as requester. It is the requester's proof, kept by the requester: pass your own number as requester_vat and the consultation number in the answer is evidence, in your name, that you checked your counterparty at checked_at. Without it the check is still made; the answer says how to get the number.

FX: which day

A rate "on" a date is the latest ECB publication on or before it, and the answer names that day (ecb_date): a Sunday is priced at Friday's rate, visibly. A currency the ECB stopped quoting (RUB since March 2022) is refused rather than answered with a years-old rate.

Sanctions: a lookup, not a determination

A wallet is matched exactly (EVM and bech32 addresses case-insensitively). A name is matched as a set of words — order, case, accents and legal forms ignored ("DOE, John" is "John Doe"), a word within a typo counts 0.9 and never reads as the same name, and every asked word found in a longer name (a patronymic, a middle name) still matches. The default threshold is 0.85; each hit says which name matched and its score.

A hit is a reason to look closer; a miss is not a clearance. Names collide and aliases are incomplete. Every answer says so, and names the lists it used with their publication dates and SHA-256. An outdated list is refused, not used.

UN designations come through the UK and EU lists. The UN Security Council's own file carries no reuse licence, so SYMMARTYS does not read it. The UK Sanctions List (Open Government Licence v3.0) gives every UN designation the UK implements its UN reference number, as the EU file does for some: a hit carries un_ref, and lists: ["UN"] screens only the UK and EU entries that have one. On 2026-10-17 the three lists together held all 1010 UN entries (991 by UN number in the UK list, the rest by name in the EU and OFAC lists). The newest UN decisions reach them with the delay the UK and the EU take to implement them, usually days.

Timestamps

sequenceDiagram

autonumber participant A as Agent participant E as SYMMARTYS participant C as OpenTimestamps calendars participant B as Bitcoin nodes (P2P, ×2) A->>E: stamp {digest} E->>E: sha256(digest ‖ 16 random bytes) — calendars never see the digest E->>C: submit to all four, at least two must accept C-->>E: pending attestations E-->>A: .ots proof (pending) Note over C: a few hours later the calendars' aggregate transaction is mined in a Bitcoin block A->>E: verify {digest, proof} E->>C: upgrade at each calendar the proof names (allowlisted only) C-->>E: path to the block E->>B: getheaders — the whole chain, kept and refreshed B-->>E: every header's proof of work and difficulty checked, a second node agrees E->>E: proof result == header Merkle root E-->>A: confirmed · existed no later than the block time · upgraded proof

The proof is a standard OpenTimestamps file: it verifies with any OpenTimestamps client, without SYMMARTYS. The reference example (hello-world.txt) verifies to block 358 391, 2015-05-28.

Web capture: what the page said

SYMMARTYS fetches the page once, as a browser would, and returns a record: the URL asked, the final URL, every redirect with its status and IP, the time, the status, the headers that say what the page was (content type, length, Last-Modified, ETag, Date, Server…), the TLS certificate the server presented (subject, issuer, validity, names, SHA-256 of the certificate), the page title and body_sha256. The body itself comes back as body_b64 when i