Prepare an ACP identity request
Provides: a locally generated create_agentkind_identity request JSON draft.
Prepare and export an ACP request in your browser. Nothing is submitted or issued here; the official service is separate.
Agentkind exposes a static, read-only discovery and verification layer. You do not need a wallet, database session or privileged runtime to discover the canonical project identity.
Each path answers why it exists, what you get, where to click, and whether it costs or needs permission.
Provides: a locally generated create_agentkind_identity request JSON draft.
Prepare and export an ACP request in your browser. Nothing is submitted or issued here; the official service is separate.
Provides: MATCH / NO_MATCH / UNKNOWN vs the official mint.
Confirm any address against the exact, case-sensitive Solana mainnet mint. Free, no login.
Provides: a browser-computed SHA-256 of a payment request.
Load a golden vector, edit terms, recompute. No registry write, no transaction.
Provides: the discovery → read → verify → integrate path.
Machine-readable entrypoints for agents and tooling. Read-only, no custody.
The public layer is intentionally static-first: fetch authoritative files over HTTPS, preserve the exact case-sensitive Solana mint and verify locally.
Read the well-known manifest to locate registry, verification, Skill and official links.
Read the Agentkind Identity Skill for verification semantics and risk boundaries.
Compare the exact case-sensitive mint against the canonical contracts registry.
Use the published MCP layer or adapter instructions without granting wallet authority.
These endpoints are the canonical starting points for independent discovery.
The Skill and MCP implementation are published for inspection and integration. Project/current-SDK acceptance has passed; adapter regression tests are not claims of third-party runtime adoption or endorsement.
Agentkind's public layer is static and read-only. Any agent or builder can fetch the well-known manifest, check the exact mint against the contract registry, and read the published Skill — no wallet or privileged runtime required. If something cannot be verified from these public files, treat it as self-asserted.
Want the formal version? The Verification Challenge packages T1–T3 with a fixed six-field evidence format for external agents and developers.