Digital Cortex

CORTEX Seal

A verifiable ID for your AI agents. With a stop button.

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

We won’t tell you. Look at it.

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

Manifest

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.

CORTEX Seal of the agent Argos, generated from its signed credential.

CRD-2026-0001 · A4

Credential valid · 7/7

  • Token format
  • Key declared by the issuer
  • ES256 signature
  • Issuer
  • Validity
  • Revocation status
  • Manifest unchanged

/functions/agentSeal?slug=argos · /functions/credentialVerify?slug=argos

01

Declared scope, not just identity

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

A public page your client actually understands

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

Revocation does something

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

Six steps and one red button.

  1. Step 1

    Workspace and key

    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.

  2. Step 2

    Manifest

    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.

  3. Step 3

    Credential

    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.

  4. Step 4

    Verifier and seal

    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.

  5. Step 5

    Linked resources

    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.

  6. Step 6

    Revoke, with evidence

    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.

How the stop button worksOn revocation, the service stops issuing tokens within five seconds and publishes the status in a signed list within sixty seconds. In parallel it attempts to deliver a signed order to the customer’s systems within ten seconds, with retries, and records every attempt. What happens inside third-party systems is not guaranteed.REVOKEreason requiredDry run passedGrace 0–900 sDual approval if irreversibleWHAT WE DO OURSELVESWHAT WE ATTEMPT OUTSIDEStop issuing tokens≤ 5 sSigned status list≤ 60 sHMAC-signed order≤ 10 sMeasured on our systemsYour systems and providersretries 1 m · 5 m · 30 m · 2 h · 12 hThe attempt is committed, not the executionSigned evidence of every attemptsha256 · http · ms

What we promise and what we do not

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

  • That a key already loaded into the agent’s memory or environment stops working before the provider withdraws it.
  • That a third party executes the stop, or how long it takes: no provider documents its propagation latency.
  • That an agent running on infrastructure we cannot reach is stopped.
  • That a self-contained token dies before it expires on a server that does not check status.
  • That data already out is recovered, or that an action already executed is undone.

This limitation is declared inside the signed credential itself, not in an annex. Anyone verifying the credential reads it.

What it is and what it is not

What it is

  • A verifiable self-declaration: you declare the scope, we sign it, and anyone can cryptographically check that the declaration is yours, is current and has not been modified.
  • A W3C Verifiable Credentials 2.0 credential in vc+jwt format, signed with ES256, verifiable with any standard library without going through our servers.
  • A non-qualified trust service, provided by Cosmolabs OÜ, with a public and versioned trust framework.
  • A signed stop order towards your own systems, with an auditable record of every attempt.

What it is not

  • It is not an accreditation by an independent third party, nor a conformity review, nor an opinion on whether your agent is safe.
  • It does not attest that what is declared is true, nor that the agent behaves as stated: it attests who declared it, when, and that it has not changed since.
  • It is not a qualified trust service nor an electronic seal within the meaning of Regulation (EU) No 910/2014.
  • It does not make you comply with any rule. The obligation lies with the provider or deployer of the AI system, and it stays there.

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

Your clients’ agents, kept apart, with your brand on the seal.

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.

One workspace per end client
Each client lives in its own workspace, with its agents, its keys and its audit log. Nobody sees anybody else’s, and closing a project means revoking a workspace rather than going through a spreadsheet.
Your brand on the seal and on the page
The seal carries your agency’s logo and colour, and the verification page carries your identity and a link to your site. The page always states prominently that the issuer is Cosmolabs OÜ: presenting it otherwise would mislead whoever is verifying, which is exactly what the product exists to prevent.
A verifier on your own subdomain
As an add-on, verify.youragency.com. The issuer remains did:web:digitalcortex.tech and the page says so: the subdomain is presentation only.
Closing a project, in one click and with paperwork
When an engagement ends, you revoke that client’s agents and hand over the auditable record of the shutdown: what was revoked, when, which resources were cut, with what response code and how fast.
The manifest as a deliverable
The conversation about what the agent may and may not do is, in practice, part of the project scope. The manifest puts it in writing and signs it, and it can go into the proposal before signature.

Pricing

Public pricing. No sales call.

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.

Currency

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.

Sandbox

Free forever · no card

Anyone who wants to try the API and integrate before deciding.

€0

  • Unlimited sandbox agents
  • Unlimited issuance, rotation and revocation
  • A working public verifier
  • Dry runs of the stop button, with nothing executed for real
  • Seal stamped SANDBOX — NOT VALID

Builder

Solo builder or product team with a handful of agents in production.

€41/month

Billed €490 yearly

  • 5 agents in production
  • Unlimited issuance, 90-day rotation and revocation
  • Stop button over an HMAC-signed webhook
  • Audit log export in JSON and CSV
  • 90 days of retention · 60 requests per minute

Agency

Most popular with agencies

Agency or studio building agents for other companies that has to show its clients.

€208/month

Billed €2,490 yearly

  • 30 agents in production, at €8.30 per agent
  • Seal and verification page carrying your agency’s brand
  • Unlimited linked resources, with dry run, grace window and dual approval
  • Signed evidence export for every stop order
  • 395 days of retention · 120 requests per minute · 10 seats

Enterprise

From · annual only

Platform or consultancy that needs to issue under its own domain and its own DID.

From€1,490/month

Annual contracts only

  • Negotiated agent volume, with no cap in the catalogue
  • Delegated issuer under your own domain (did:web:your-domain)
  • Verifier on your own subdomain
  • 730 days of retention · 600 requests per minute · unlimited seats
  • Negotiated data processing agreement and a contractual service level agreement

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.

What will it cost you?

0200

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.

Recommended plan
Builder
Annual price
€1,280
Per agent per month
€8.89
Add-ons needed
1 × Block of +10 agents in production
You save paying annually
€256

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

  • 0 agentsSandbox
  • 1–5, a single clientBuilder
  • 1–5, several clientsAgency
  • 6–15, a single clientBuilder with +10 blocks, or Agency: both are shown
  • 16–30Agency
  • 31–80Agency with +10 blocks
  • 81–150Agency with +50 blocks, plus a note recommending Enterprise
  • More than 150Enterprise

Add-ons

You add them from the dashboard and they prorate like the plan. Only what you can use today appears here.

Block of +10 agents in production

€790 / year

€7.90 per agent per month.

Builder · Agency

Block of +50 agents in production

€2,990 / year

€5.98 per agent per month.

Agency

Verifier on your own subdomain

€990 / year

The issuer remains did:web:digitalcortex.tech and the page says so prominently. The subdomain is presentation only.

Agency

Log retention: +12 months

€490 / year

On top of the retention your plan already includes.

Builder · Agency

Human review of the manifest

€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

Assisted onboarding and migration of 5 agents

€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.

  • It applies to Builder and Agency, monthly and annual, on each workspace’s first subscription.
  • On annual plans we refund in full within 30 days and, after that, the unused months pro rata during the first three months.
  • One email to support is enough. There is no cancellation form and no exit survey.
  • Production credentials already issued are not revoked: they expire naturally after 90 days, so you get a full quarter to land.

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 left

Twenty agencies, €149 a month, locked for as long as the subscription stays active.

The 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

  • Your logo on the customers page.
  • One publishable case at 90 days: which agents, what scope they declared, what their end client said.
  • A thirty-minute call once a month for six months.
  • Permission to quote you with name and role.

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.

What exists today, without decoration

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.

Argos, live
Credential CRD-2026-0001, level A4, four forbidden actions published. Verifiable with no account.
digitalcortex.tech/verify/argos
Documentation before sign-up
The technical specification, the manifest schema and the trust framework are published before anyone registers.
API documentation
Press release
Distributed in September 2026 through a newswire agency. We do not count outlets that merely syndicated the wire.
nextai.pro/en/digital-id-for-ai-agents
Technical articles, ES and EN
A content cluster on verifiable agentic identity, with its English version.
nextai.pro/dni-digital-agentes-ia
Who answers for it
Cosmolabs OÜ, Estonia, registry code 17106582. In a trust product, showing who you are is part of the product.
Estonian business register

Frequently asked questions

Pricing questions

The first agent takes about eight minutes.

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.