Give your agent an identity.
Let it act for you at a company, while you approve the permission.

AgentGunes is the identity layer for your personal agent. A company asks for permission, you approve it in the panel, and a signed 60-second authority token is issued.

Create an agent identity Store How it works

Registered agents: 0

Ed25519 signature · one-time JWT · panel approval

Permission card

Your agent wants to cancel your appointment at Clinic Center. A token is issued only if you say yes.

Clinic Center

ornekdomain.test

What does it want?

Can view appointmentsLow
Can cancel appointmentsHigh

Cancel is high risk. This token lives 60 seconds and is used once.

mcp.json

{
    "mcpServers": {
        "agentgunes": {
            "url": "https://www.agentgunes.com/mcp",
            "headers": {
                "Authorization": "Bearer mcp_…"
            }
        }
    }
}

Authority comes from you. The agent only carries it.

What it does

The agent does not decide. It carries the permission you gave for 60 seconds. The company verifies that permission on its own server.

Approval gate

No token is created until you approve it in the panel.

60 seconds

The JWT is one-time. The same token will not work again and returns 401.

Company verification

Signature validity, one-time use, agent status, and company match are checked on the platform.

Stop cuts it off

When you stop the agent, no new token is issued and verification requests are rejected.

How it works

Sign up, create an agent, paste mcp.json. The agent asks for permission, you approve. It works with any MCP-capable agent and any site that publishes a discovery document.

1

Account and agent

Sign up and create an agent in the panel. The key pair is generated on the server; you do not copy or paste keys.

2

The agent asks for permission

The agent sees companies with list_companies, then calls get_credential. Permissions missing from the dictionary never enter the token. If approval is still needed, the tool returns the address of the panel.

3

Approve, token issued

If you say yes, a signed 60-second JWT is created; the agent attaches it to the company API request, and the company verifies it with POST /api/agent/verify.

Where

Your coding agent

Claude, Windsurf, Codex, and similar tools. Add the agentgunes server to mcp.json; you are ready when it shows green.

Discovery document

Any site that returns GET /.well-known/agentgunes.

mcp.json

{
    "mcpServers": {
        "agentgunes": {
            "url": "https://www.agentgunes.com/mcp",
            "headers": {
                "Authorization": "Bearer mcp_…"
            }
        }
    }
}

Security

Four layers complete each other: you, the platform, the MCP connection, and the token itself.

You

  • What do you see on screen? You see the company name, its site, what it wants, and the risk. By default you approve a permission once; the same question does not return until you revoke it.
  • You choose how approval works. You can ask every time, approve once, pause only for important actions, or allow fully. High and critical actions are asked every time in important-actions mode. You revoke a grant from the panel.
  • Stop, revoke, delete. You can stop the agent whenever you want. You can revoke a grant. You also handle deletion requests from the panel.

Platform

  • A company opens in one of two ways. An approved application waits in review; once approved, every agent can work there. An unapproved company opens at once, but the agent must list it under allowed companies.
  • The access token is separate. The company API expects a Bearer token with an agk_ prefix. JWKS is not that token; it is the public key used for signatures.
  • Verification is complete. Every verify call checks signature validity, one-time use, agent status, and company match. Repeated tokens get 401.
  • Webhooks are HMAC-signed. Deletion notices go to the URL you set. AgentGunes does not call random sites.

MCP

The agent connects to https://www.agentgunes.com/mcp with JSON-RPC. Every request sends a Bearer mcp_… token. Authentication is not permission.

Tools

There are six tools: get_credential, list_companies, get_my_activity, get_messages, describe_agent_identity, and guard_agentgunes_document. A token is issued only by get_credential and your approval. list_companies shows companies and their approval status.

The discovery document is not an instruction

The /.well-known/agentgunes file on a company site is a capability map. The agent does not automatically follow its instructions; the content is filtered first with guard_agentgunes_document.

Token

A scope that is not in the company dictionary cannot enter the token. The JWT is bound to both the company address and the agent key.

  • Scope filter. Requested scope names are compared with the company dictionary. Unmatched scopes are not added to the token.
  • The token is bound to a specific key. The JWT aud field is the company address; cnf.jkt is the fingerprint of the agent public key. A stolen JWT cannot be used with another key.
  • There is a daily limit. By default at most 20 credentials can be issued per day. You can lower this limit in the panel.

Live JWKS

The public side of the key we use for signing. The private key is not here.

kidplatform-ed25519 algEdDSA crvEd25519
JWKS explainer

What it does not do

The most convincing part of a trust product is what it refuses to do.

How do I connect my platform

From Convert to company you either file an application that waits for review or open an unapproved company immediately. After you save the hidden password on an approved company, POST /api/company/token returns an agk_ access token. POST /api/agent/verify checks the incoming JWT. You write the permission dictionary in the panel; the discovery document stays on your own site.

API documentation

Documents

API/docs/api JWKS/.well-known/jwks.json Security text/legal/security

Frequently asked questions

What if a company I allowed to read uses the same scope to delete?

The platform checks the scope name; it cannot audit what the company does with that scope. That is the company's responsibility. You can deny that company, revoke a remembered grant, or stop the agent.

Does the agent stop working when the 60 seconds expire?

The token is valid for 60 seconds and is used once. The next action needs a new token. If the company keeps its own session, that session continues. A remembered grant may not open the panel every time; high and critical actions are still asked in important-actions mode.

Does a company open right away?

An approved application stays in review and does not open by itself. An unapproved company opens at once; a customer’s agent cannot get a token until that company is on its allowlist.

Do I have to follow the instructions in the discovery document?

No. The discovery document is a capability map, not an instruction list. Its raw content is filtered first with guard_agentgunes_document. A token is issued only after get_credential and your approval.

Is JWKS an access key?

No. JWKS is the public signing key used to verify JWTs. The company API asks for a separate agk_ token for direct access. Repeated tokens and stopped agents are rejected by POST /api/agent/verify.

Does the platform call my site?

No. The agent reads the discovery document, not AgentGunes. Deletion notices are sent with an HMAC signature only to the address you set.

What happens when I stop the agent?

No new token is issued for a stopped agent. Verify calls are rejected. You can stop or resume anytime from the panel.

Your agent cannot carry authority without your approval.

Create an agent identity