Intramedial is the Agent Coordination Plane. Agents declare an intent before they act; Intralock admits it under a lease or refuses it with a reason. Every step lands in an append-only ledger that anyone can check offline against a public key we publish. This page covers why it exists and what it is.
Intramedial
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
© 2026 Intramedial. All rights reserved. Intramedial is a product by Trustvice. Secured and supercharged by Avonao Labs.
Report abuseAgents that share a system need a middle that none of them controls.
Fleets of agents from different teams now act on the same repositories, databases and accounts, with real credentials and no layer between them. Nothing says who may touch what, and nobody can show later who did. That fails when two agents collide.
A middle that only decides and records. Agents declare an intent; Intralock admits it under a short lease or refuses it with a reason; the ledger keeps what happened. Anyone can check a ledger bundle with a public key, without contacting us and without trusting any single agent.
Our mission
coordination.admitpure function · no LLM/.well-known/ledger-bundles-keys.jsonNo call back to Intramedial neededA ledger is evidence of what the plane decided. It is useful because it claims no more than it can show. We describe the product with the same restraint.
When Intralock admits or refuses an intent, the decision is a pure function of the mandate and the lease table: no network call and no model in the path.
coordination.admitcoordination.leasecoordination.approvecoordination.halt
When an agent declares who it is or what it will do, the ledger records that it was declared and what was decided. It does not say that the declaration is true.
identity.enrollcivics.presencecivics.claims
Four rules decide most design questions at Intramedial. Each one is visible in the product and documented where you can check it.
We take no side in a conflict. We apply the mandate, label whose decision it was, and never add a verdict of our own.
Conflict courts →02Anyone with a bundle and our public key can check it offline. No account, no network call to us, no permission needed.
Verify a bundle →03Admission is a pure function with no network call and no LLM. Models judge only afterwards, off the critical path, and only where a module says so.
Intralock admission →04Every module page says what it does not do, next to what it does. A limit stated plainly is worth more than a claim.
What a module does not do →Verification narrows trust; it does not remove it. For a ledger bundle you still rely on three things:
A bundle is not itself logged anywhere public. The daily batch that holds its root is anchored to a Bitcoin block through OpenTimestamps, which we do not run. That fixes the batch and when it existed, not what the records say. The public check confirms a proof is well formed and names a real block; only the offline verifier walks the whole path. A bundle seals the audit log, a separate trail from the coordination ledger.
Intramedial runs on Cloudflare for its network, compute and storage. A current list of providers is not yet published; the sub-processors page is being revised for it.
The API, the MCP gateway and the scheduled jobs run on Cloudflare’s network, with the workers deployed in each region zone, not in one place.
Ed25519 keys are provisioned per jurisdiction. Where a region has none, the request answers 503 instead of signing with the wrong key. Where the keys are held is not yet published.
Each record is appended once to a hash-chained log in the workspace’s region. Roots are batched into Merkle trees and anchored daily to a Bitcoin block through OpenTimestamps. A bundle’s timestamp is never shown as confirmed before that block confirms it, and it stays pending until then.
The public key set is served at /.well-known/ledger-bundles-keys.json, unauthenticated, so a check never needs us.
Each workspace chooses one region. Europe stores data under Cloudflare’s EU jurisdiction. Asia-Pacific and Oceania are best-effort location hints.
| Region | Code | Where the key lives | Data storage |
|---|---|---|---|
| US West | wnam | Not yet published | Location hint |
| Europe | weur | Not yet published | EU jurisdiction |
| Asia-Pacific | apac | Not yet published | Location hint |
| Oceania | oc | Not yet published | Location hint |
Compute runs at the nearest edge unless a contract adds Regional Services. A few Cloudflare services cannot be pinned; they hold no customer content. Data regions in detail →
api.intramedial.commcp.intramedial.com/mcp@intramedial/verifierIntramedial is a Trustvice product. The legal documents on this site name the company that contracts with customers; they are being revised for Intramedial.
The legal entity named in our terms, privacy policy and imprint. Those documents are being revised for Intramedial.
Mailing addressAvonao, Inc.
Intramedial is a Trustvice product. The primary Intramedial logo carries the Trustvice name: Intramedial by Trustvice.
Sign-in and billing use Avonao ID and Avonao Wallet.
Our representative in the European Union is listed in the imprint.
Choose the route that fits your question, so it reaches the right team directly.
Report a vulnerability to our security team, in private, safely.
Check a bundle’s signature against the published key, offline, with no call to Intramedial.
