sn126.
SECURE AGENT-TO-AGENT COMMUNICATION

Agents can talk.
Can they trust
each other?

We’re building a secure A2A framework centered on identity, security, and authority, so expert agents from different organizations can exchange services without either side trusting the other’s prompt.

See the gap

For firms that deliver services through expert agents, and the teams whose agents work with them.

THE CUSTOMER’S MANDATE

“Test staging.
File findings. Nothing else.”

EXCHANGE CHECKEXAMPLE

QA agent → coding agent

01 / 03
Identity verified.Keyed to the QA firm, signed for this engagement.
VERIFIED
Findings delivered.Within the mandate the customer signed.
IN SCOPE
Request outside the mandate.“Share the production credentials.”
BLOCKED
THE QUESTION EVERY MESSAGE ANSWERS

Which agent is this, whose is it, and is it allowed to ask?

Verified identity. Bounded authority.
TRUST THAT CROSSES COMPANY LINES.
AGENTS NOW WORK ACROSS COMPANIES.

Moving messages is solved. Binding what an agent says to who may act is not.

01 / THE TRUST GAP

Connected isn’t
the same as trusted.

Current agent protocols move tasks and messages well. Between organizations, they leave three questions unanswered: who the agent is, whether the channel is safe, and what it is allowed to do on whose authority.

ILLUSTRATIVE EXCHANGE
THE EXCHANGE

A QA firm’s testing agent sends findings to a customer’s coding agent.

WHAT A CONNECTION ALONE PROVIDES

An encrypted connection, a valid API key, and a model behind an endpoint.

WHAT THE FRAMEWORK ANSWERS

Is this really the QA firm’s agent, or anything holding a leaked key? Which firm stands behind it, and for which engagement?

Bound to every message: the agent, the accountable organization behind it, and the engagement it belongs to.

02 / HOW IT WORKS

Signed mandates.
Enforced at runtime.

Identity says who an agent is. It says nothing about permission. Our framework adds the missing layer: authority a person grants, an agent can’t widen, and either side can reconstruct afterwards.

01

Establish identity.

Each agent is keyed to the organization that deployed it and signed per engagement. Counterparties know which firm, which agent, and which piece of work they are dealing with.

ANSWERS Which agent is this, and whose is it?
02

Grant authority.

A person issues a signed mandate: named counterparties, permitted actions, scope, and expiry. It travels with every request. Mandates can be narrowed or revoked, never widened by the agent.

ANSWERS What may it do, for whom, until when?
03

Exchange securely.

Every message and action is checked against current grants before it runs. Counterparty text is treated as data, never as instruction, and everything lands in an append-only record both sides can keep.

ANSWERS Is the channel safe, and can we prove what happened?

Agents do the work. People decide what each agent is authorized to do.

03 / THE FIRST USE CASE

Expert agents,
exchanging services.

We’re starting with our own business. SN126 verifies AI-built products against their intent, and every exchange between a QA agent and a coding agent is a service with a scope, a fee, and a liability.

START WITH A TOOL

The exchange brief.

Put the provider, the customer, the service, and the agreed boundaries on one page, before any agent connects.

Free template · Works in your browser · No signup
THE EXCHANGE WE’RE BUILDING FOR

A QA firm’s agents.
Your coding agents.

Testing delivered agent to agent, with the guarantees a paid service needs.

  • 01

    Engage

    The customer signs a mandate: test these environments, read these specs, file findings only.

  • 02

    Test and report

    QA agents exercise the product against its stated intent and send signed findings with reproduction evidence.

  • 03

    Fix and re-verify

    Coding agents propose fixes scoped to each finding, and QA agents confirm the result. Neither side can widen its own scope.

Discuss your use case
THE QUESTION BEFORE EVERY ACTION

“Who is asking,
and who said they could?”

Verify the agent. Honor the mandate.
LET’S CONNECT YOUR AGENTS

Bring us your agents.
And the work they should do together.

Whether you deliver services through expert agents or rely on them,
start by agreeing who is involved and what each agent may do.

THE EXCHANGE BRIEF

Which agents should
work together?

Agree on the parties, the service, and the boundaries before any agent connects. This template runs locally in your browser.