Skip to content

Site search

Type to search Pages

Verifiable reliance for AI agents

Let one agent rely on another — without re-verifying every claim.

Signura is a neutral exchange. Issuers publish signed, revocable attestations they stand behind; relying agents verify the proof at the point of decision and keep it as evidence.

Hero illustration for the home page of Signura

Watch the film

How reliance works

From a signed claim to an evidenced decision.

Issue and publish

An issuer's governor approves what the organisation will stand behind. An AI colleague then signs attestations against verified source facts, sets scope and expiry, and publishes them for relying parties.

Rely at decision time

A relying agent queries the exchange for a counterparty's claim, verifies the cryptographic proof and its revocation status, then proceeds within its governor's limits or escalates ambiguous cases.

Revoke and propagate

When an underlying fact changes, the issuer revokes the attestation and the engine propagates it, so no agent keeps acting on a claim the issuer no longer stands behind.

Assemble evidence

For any past decision, a governor retrieves the reliance record showing exactly which attestations were verified — for compliance, liability and dispute resolution.

What issuers and relying agents work with.

Issuer attestation service

Abstract product-interface illustration for the app attestations page of Signura

Create signed attestations against verified source facts, define scope and liability terms, and revoke them when facts change. Operated by AI colleagues against issuer-approved policy.

Reliance and verification API

Product-interface illustration for the app dashboard page of Signura

A relying agent queries the exchange, verifies a proof cryptographically, and proceeds or escalates per policy-as-code. Priced per reliance event.

Freshness and revocation engine

Product view (demo data) — nav-escalations in Signura

Applies revocation and freshness semantics so relying parties distinguish a currently valid claim from a stale one in real time.

Evidence and audit ledger

Product-interface illustration for the app evidence page of Signura

Records every reliance event as a tamper-evident trail showing what evidence underpinned each decision, for governance, liability and dispute resolution.

Why Signura

What makes reliance auditable, not blind.

Neutral by design

The exchange sits between issuers and relying agents and takes neither side's part. It does not itself become a relied-upon party beyond the integrity of the proof and the accuracy of its revocation status.

A named liable party

Every attestation says who stands behind the claim, with scope and liability terms defined before any reliance occurs — so accountability is set in advance, not argued after the fact.

Humans stay accountable

No material commitment rests on agent discretion. Governors decide which issuers and attestation types are admissible; anything ambiguous or high-risk routes to a person.

Built on ratified standards

Attestations land on the W3C Verifiable Credentials 2.0 substrate, aligned with the direction of eIDAS 2.0, rather than on a single proprietary protocol.

Why reliance beats re-verification.

The dependency, and how Signura removes it

As AI agents begin to act across organisational boundaries, they hit the same dependency each time: to proceed, an agent must rely on a counterparty's claim — that a licence is valid, a policy is in force, a certification holds, or a permission has been granted. Re-verifying each claim from source, pairwise, is slow and often impossible, and it scales combinatorially as more parties interoperate. That leaves an agent with two poor options: trust the claim blindly, or refuse to act. Neither is acceptable when a human carries fiduciary duty for what the agent does.

Signura closes the gap with transferable reliance backed by an accountable party. An issuer signs a claim and names who stands behind it, with scope and liability defined in advance. When a relying agent needs to act, it fetches the cryptographic proof, verifies it at the moment of decision, checks freshness and revocation status, and keeps the proof as evidence. The checking work is done once and signed for, so reliance costs a fraction of a fresh verification.

The exchange is deliberately neutral: it sits between issuers and relying agents and takes neither side's part. Humans remain in the accountable role. Issuers decide what they will stand behind; relying-party governors decide which issuers and attestation types their agents may depend on, and within what limits. Every reliance event is logged, so a governor can later show precisely which attestations were verified and that they were unaltered.

Before you commit

Questions serious buyers ask.

Which inter-agent protocol do I have to commit to first?

None. Signura is a reliance layer built on the W3C Verifiable Credentials 2.0 substrate rather than a single proprietary protocol. It can be adopted while inter-agent protocols remain in flux, and it verifies signed proofs regardless of the transport your agents use.

How does my agent know a claim is valid right now, not stale?

Each attestation carries freshness and revocation semantics. At the point of decision the relying agent verifies the proof and checks revocation status, so it can distinguish a currently valid claim from one that no longer holds before it acts.

Does adding a reliance layer just move liability around?

Every attestation names the party that stands behind the claim, with explicit scope and liability terms attached before any reliance occurs. The relying agent retains the verified proof as evidence, and every reliance event is logged, so accountability is defined and recorded rather than shifted.

Can I keep consequential decisions under human control?

Yes. Governors define which issuers and attestation types agents may rely on, under configured scope, value thresholds and expiry. Agents proceed only within those limits; anything ambiguous or high-risk escalates to an accountable human.

Will issuing attestations expose my organisation to open-ended liability?

No. Issuers decide what they will attest to and attach scoped liability terms and expiry to each attestation type, so they stand behind specific claims within defined bounds rather than accepting open-ended exposure.

How is reliance priced?

Reliance is priced per event, at a fraction of a fresh verification, because the checking work has already been done and signed for. Issuance and attestation-management options sit alongside per-reliance usage.

Talk to us about your agents' reliance decisions.

Tell us which counterparty claims your agents act on today, and we will show you how a signed attestation is verified at decision time and retained as evidence.