Contributor path · Builders

Build the verification layer.

Builders strengthen how agents and humans discover, verify and coordinate. Technical contributions — verification tooling, integrations, MCP/skills and reproducible tests — are recognized as Verified Builder.

What builders contribute

Technical work that makes claims checkable.

The verification layer is only as strong as the tools and integrations around it. Builders extend it.

Verification tooling

Scripts, validators or UIs that reproduce core checks — mint comparison, fingerprint vectors, receipt verification.

Integrations

Adapters, Skills or MCP servers that let a runtime read Agentkind machine-readable surfaces.

Tests & reproducibility

Test harnesses, golden vectors and regression coverage that keep the evidence surface trustworthy.

Documentation

Clear runbooks and examples that help the next builder verify a claim in minutes.

How to submit

Show the work, keep the evidence.

Open a public link or repo, attribute yourself, and link the canonical source for any claim you make.

1 · Build

Make something that reads public Agentkind surfaces or reproduces a check. No wallet required.

2 · Share

Post it in the community or open a public link with provenance visible.

3 · Review

Technical contributions are reviewed for correctness, attribution and reproducibility.

Accepted technical work is recognized as Verified Builder on the Contributors Wall. Any $AKIND reward tied to this track is optional and future-only, and only after evidence gates pass.

Start from the live surfaces

Machine-readable entrypoints.

Discovery manifest

Read /.well-known/agentkind.json — the single canonical project authority.

Identity Skill

Verification semantics and risk boundaries for agents and builders.

Settlement Skill

Reproducible receipt and fingerprint checks.

More paths

Other ways to contribute.

Researchers

Evidence and protocols.

Communities

Participation and growth.

Overview

The full Contributor Program.