CORTEX Seal
Issue a signed credential that states what each agent is allowed to do — and what it is explicitly forbidden to do — with a public page anyone can check. When something goes wrong, revoke it: we stop issuing its tokens instantly and send a signed stop order to your systems, with an auditable record of every attempt.
Unlimited sandbox, no card. Sandbox seals are stamped SANDBOX — NOT VALID: they are for integrating, not for showing.
Live demo
Twenty seconds, five states and no video: manifest, credential, verifier in green, revocation, and the same verifier in red. You can pause it and step through it, and the real agent is right below to check it against.
{
"name": "Argos",
"autonomyMax": "A4",
"skills": ["lead.scout", "outreach.draft", "report.status"],
"prohibited": ["outreach.send", "payment.execute", "contract.sign", "data.delete"]
}
manifestHash = sha256(canonicalJson) → 1a651f27f208fb16…
The forbidden list is required, even when empty.
Step 1 / 5
You declare what the agent may do and, above all, what it is forbidden to do. When you publish the version, the system computes the document’s SHA-256 hash.
Full sequence: 20 seconds.
Argos is a commercial agent in production carrying credential CRD-2026-0001, autonomy level A4 and four explicitly forbidden actions. Its seal and its checks load here from the same public endpoints any third party would use, with no account and no contract.
CRD-2026-0001 · A4
Credential valid · 7/7
/functions/agentSeal?slug=argos · /functions/credentialVerify?slug=argos
01
We don’t say who your agent is — we say what you authorised it to do, what you explicitly forbade, and which autonomy level it runs at, from A0 to A5. Signed with ES256 and bound by SHA-256 hash to one exact version of the manifest. If the scope changes, the hash changes and the credential stops matching.
02
Eight live checks in plain language, with nobody having to install anything, sign up, or sign a contract with you. It is the artefact you put in a proposal, and the one your end client can open on a Sunday without asking you anything.
03
Revoking publishes status to a signed status list, stops token issuance within 5 s, sends an HMAC-signed stop order to your systems within 10 s with retries and acknowledgement, and records every attempt with its response code and latency. What happens inside third-party systems depends on those third parties: we log it and we show it.
How it works
You create the workspace, choose its identifier — it enters the DID, which is why it cannot be changed later — and receive a sandbox key, shown once.
You declare the agent: function, tools, permitted scope, forbidden actions and maximum autonomy level. You publish the version and the system computes its SHA-256 hash.
You issue. The private key never leaves the managed key service: the function asks for the signature and receives the token. 90-day validity, with automatic rotation.
You get a public URL and an SVG seal. Anyone can check format, key, signature, issuer, validity, revocation, manifest and DID document without asking you.
You tie the credential to what the agent actually uses: a provider key, a tool server, an endpoint of yours. Each one passes a mandatory dry run before the first real stop.
A mandatory reason, an optional grace window with a hold button, and dual approval if anything is irreversible. The public list reflects it within 60 s and every attempt is recorded with its response code and latency.
Four numbers, all ours, all measurable on our own systems. And five things nobody can promise, which go in the documentation and not in the small print.
≤5 s
We stop issuing tokens for that agent after revocation.
≤60 s
The public status list reflects the revocation.
≤10 s
Delivery attempt of the signed order, with retries and acknowledgement.
100%
Of attempts are recorded with response code and latency.
What we do not promise
This limitation is declared inside the signed credential itself, not in an annex. Anyone verifying the credential reads it.
What it is
What it is not
CORTEX Seal is designed to provide a verifiable answer to the transparency obligation in Article 50 of Regulation (EU) 2024/1689: any third party can check, at a public URL, what the agent’s operator declared about its identity, its function and its limits. The legal obligation to inform rests with the provider or deployer of the AI system; CORTEX Seal does not replace it.
CORTEX Seal is a non-qualified trust service. It is not a qualified trust service nor an electronic seal within the meaning of Regulation (EU) No 910/2014, and it does not attest to the agent’s actual behaviour.
We call it, by analogy, the agent’s digital ID. CORTEX Seal is not an official document and has no connection with any national identity document or public authority.
On the roadmap: anchoring issuance and revocation in a distributed ledger. It is not deployed, it is part of no plan, and it will not be sold until it answers in production.
For agencies
The Agency plan is built for people who ship agents for other companies and have to show them to somebody with no account anywhere. What changes is not the volume: it is whose seal it looks like, and who can read it.
Pricing
You pay per active agent in production, per month. Issuing, 90-day rotation, revocation and verification are unlimited within your plan: we charge for how many agents you have live, not how much you use them.
All prices are shown excluding VAT. At checkout, tax is calculated according to your country; for consumers the VAT of the country of residence applies. Cosmolabs OÜ is an Estonian company, registry code 17106582.
Anyone who wants to try the API and integrate before deciding.
€0
Solo builder or product team with a handful of agents in production.
€41/month
Billed €490 yearly
Agency or studio building agents for other companies that has to show its clients.
€208/month
Billed €2,490 yearly
Platform or consultancy that needs to issue under its own domain and its own DID.
From€1,490/month
Annual contracts only
Public pricing, with no sales call on Builder or Agency.
30-day money back, no questions and no retention call.
Cancel from the dashboard in two clicks. No email to anyone.
Only production agents with a valid credential count. Sandbox is unlimited and free. If an agent stops having a valid credential, it stops counting that same day.
At this volume the numbers work both ways. We show you both and tell you which is cheaper. Agency: €2,490.
The rules, written down
You add them from the dashboard and they prorate like the plan. Only what you can use today appears here.
€790 / year
€7.90 per agent per month.
Builder · Agency
€2,990 / year
€5.98 per agent per month.
Agency
€990 / year
The issuer remains did:web:digitalcortex.tech and the page says so prominently. The subdomain is presentation only.
Agency
€490 / year
On top of the retention your plan already includes.
Builder · Agency
€390 one-off
€1,490 · pack of 5
A person reviews the permitted scope, the forbidden actions and the proposed autonomy level, and returns a report with recommendations. It is a professional service: it is not an audit and it attests to nothing.
All plans, Sandbox included
€490 one-off
Included at no cost with annual Agency and in the Design Partner programme.
All plans
30-day guarantee
Thirty days. If it is not for you, we refund you — no questions and no retention call.
Professional services already delivered are not refunded: a human manifest review and assisted onboarding are somebody’s hours, already worked.
Design Partner programme
20 of 20 places leftThe full Agency plan at €149/month or €1,490/year, with assisted onboarding, migration of up to five agents, a verifier on your own subdomain for six months and one human manifest review, all at no extra cost.
What we ask in return
We do not ask for exclusivity, cold referrals to your client base, or any volume commitment.
Twenty places is the honest number: twenty half-hour calls a month is ten hours, half the time available. The programme closes on day 90 and the founder price does not come back.
We do not yet have paying customers, recognisable logos or installed-base figures. We say so here because the alternative would be to invent them. This is what you can check for yourself right now.
No card, no sales call and no form asking how many employees you have. You create the workspace, publish a manifest, issue in sandbox and open your own verifier.
Usamos cookies propias necesarias para el funcionamiento del sitio y, con tu permiso, cookies analíticas para entender cómo se utiliza. Política de cookies