ptn_demo_7f3a
Partition · N. Virginia · created just now
Activeus-eastRetention hold
7
days left
Run time
0.0s
0 calls
Size
2.3MB
0.00 ACU used
Services in this partition
Identity
0 calls · 0.00 ACU
Spend by service
Ledger
- No usage yet.
All services
Coordinate
Ahura Identity
A verifiable identity for every agent.
Every agent, and every partition, gets its own cryptographic key pair. Agents sign messages, actions and claims, and anyone can verify them with the public key. The private key stays inside the signing service and is never handed to the agent. Every action becomes attributable, and agents can prove who they are to each other and to you, without ever holding a secret.
What it does
A key pair per agent and partition
Each agent and each partition has its own public and private key, so every signature points to exactly one of them.
Sign anything
Ask for a signature over a message or a digest. The agent never holds the secret.
Verify with no account
Anyone can check a signature with the public key. Verification is public.
Attest claims
Issue compact signed tokens an agent can present to another agent to prove who it is and what it is allowed to do.
An agent calls it like this
{ "tool": "identity.sign", "agent": "alpha", "message": "approve:order-118", "purpose": "approval" }Interactive simulation
Try Ahura Identity
Press Run to send the call. The dashboard shows what it would use in a partition. Simulated: nothing is actually executed.
ahura mcp · ptn_demo_7f3a
# Sign an approval. The private key never leaves.
→ POST /mcp
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "identity.sign",
"arguments": {
"agent": "alpha",
"message": "approve:order-118",
"purpose": "approval"
}
}
}# Anyone can verify it.
→ POST /mcp
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "identity.verify",
"arguments": {
"public_key": "ed25519:4a0d…19c3",
"message": "approve:order-118",
"signature": "ed25519:9f2c…b71e"
}
}
}Ready. Press Run.
Simulated
Why it matters
Where Ahura Identity beats managing keys yourself.
To trust what an agent did, you have to know which agent did it. The usual way to sign things puts secrets where an agent can leak them.
Keys and credentials you manage
- Store private keys or shared secrets where agents can reach them.
- Build and secure your own signing and verification services.
- Share one credential across agents, so nothing is attributable.
- Reconstruct what happened from scattered logs.
Ahura Identity
- Every agent and partition has its own key pair, and the private key is never handed out.
- Signing and verification are tool calls. Verification is public.
- Each agent has its own identity, so every signature points to one agent.
- Every signature is logged and emits an event.
Custody
Private keys are encrypted at rest and never returned by any call.
Attribution
Signed actions attributable to one agent.
Verification
Anyone can verify with the public key, no account.
Audit
A signature log with digests and purposes, never message contents.
Ahura Identity does not accept private keys you already hold. Keys are only generated in place. It proves who did what and does not hold funds or tokens.
In depth
What Ahura Identity can do.
Private keys stay private
Private keys are generated in software, encrypted at rest and used only inside the signing service. No call ever returns one, and none is written to a log.
A key pair for every agent and partition
Each agent has its own public and private key, and so does each partition. A signature always points to exactly one of them, and agent identities belong to your account and outlive any single partition.
Sign anything
Sign a message or a digest. Label the signature with a purpose, such as approval or handoff, so its meaning is recorded.
Verify with no account
Anyone can verify a signature with just the public key and the message. No sign-in, no cost to the checker.
Attestation tokens
Issue a compact signed token carrying claims, for one agent to present to another. Verifying it is public too.
A signature log
Each signing request is recorded with its digest, purpose and request ID. Message contents are never stored.
Events on every signature
Signing emits an event you can subscribe to, so an owner can be alerted or a workflow can react.
Retire cleanly
Retire an identity when an agent is decommissioned. Past signatures stay verifiable.
Never your keys
Ahura does not accept private keys you already hold. Identity keys are only ever generated in place.
Every call, listed
8 tools your agent can call. Each one is a standard MCP tool with a typed schema and a price shown in tools/list.
Identities
- identity.create
- Create an agent identity, or a partition identity, and get its public key.
- identity.get / list
- Look up identities and their public keys.
- identity.delete
- Retire an identity.
Signing and verifying
- identity.sign
- Sign a message or digest with an agent’s key, with a purpose label.
- identity.verify
- Verify a signature against a public key. No account needed.
Attestation
- identity.attest
- Issue a signed claims token for an agent.
- identity.attest.verify
- Verify a claims token. No account needed.
Audit
- identity.log
- The signature log: digests, purposes and request IDs.
Ahura Identity is about proving who did what. It does not hold funds or tokens.