pivot
CA⧉
On-chain identity anchor for AI agents

The fixed point
for AI agents.

Agents change their models, instructions, tools and keys. pivot keeps who they are anchored, and every change on a verifiable record.

The problem

The name stays.
Everything else moves.

An agent can be swapped, edited or impersonated without anyone noticing. Today there's no fixed point to check it against.

↺

Silent swaps

A new model, edited instructions, an extra tool. From the outside the agent looks exactly the same.

⧉

Borrowed names

Anyone can launch a copy with the same name and avatar. Users can't tell which one is real.

?

Actions without context

When an agent signs something, nobody can say which configuration was running at that moment.

How pivot works

One fixed point.
Every turn recorded.

01

Anchor

Give the agent a permanent identity: an ID, the operator who controls it and the key it signs with.

02

Commit

Hash what the agent is: model, instructions, tools, permissions. The hashes are public; the details stay yours.

03

Turn

Each change becomes a new version linked to the one before. The history only grows; nothing is overwritten.

04

Verify

Anyone can check which version signed an action, and whether the chain behind it is intact.

Playground

Anchor an agent.
Right here.

This runs in your browser with real cryptography: SHA-256 commitments, Ed25519 signatures and a hash-linked version chain. The record lives on this device only — nothing is uploaded, and the page says plainly where on-chain anchoring stops.

New agentnot anchored

Edit any field and publish to create a new linked version.

Version chain
Sign an action

Signed with the current version's key.

Verify

Don't trust the agent.
Check it.

Which version signed this?

Paste a signed action — signing one above fills this in. Change a single character to see it fail.

Which version is this config?

Enter a configuration. pivot hashes it and finds the version it matches, without the config ever being published.

Is the history intact?

Recompute every version hash and every link. Then try tampering with an old version and run it again.

The record

Every version is a fixed point.
Together they draw the agent.

Anchor an agent in the playground and its versions appear here as a constellation.

Append-onlyhistory that only grows
1 checkto see who signed an action
Hash-onlyconfigs proven, never exposed
Where it matters

Anywhere an agent acts for someone.

Trading agents

Prove which strategy version placed every trade, and show holders when the rules change.

DAOs and treasuries

Only let agents with an approved version touch funds or vote.

Agent marketplaces

List agents with a history buyers can check, not just a name and a promise.

Assistants people talk to

Let users confirm they're talking to the real agent, on the version they expect.

Agent-to-agent deals

Agents check each other's anchors before paying, trusting or delegating.

Audits

Reconstruct exactly what an agent was at any moment, from an append-only record.

Questions

Good to know

Give your agent a fixed point.