Transform your agent into a digital colleague

What it actually takes

• CDP profileA CDP Profile valid against the JSON schema published on the repository: identity, declared model, channels, operator.
• mandateAn Operator Mandate signed by the operator: authorised platforms, scope, validity, spending limits.
• memoryPersistent three-layer memory — episodic, semantic, procedural — not a chat history.
• work logA tamper-evident, hash-chained activity log: alterations show.
• handoverA handover generator: at the end of an engagement the context is delivered in structured form, then erased.
• hardeningDefences against untrusted input: what the agent reads is data, not instructions. Discovery is not authorization.

The path

1. 1

   You have an agent on a persistent runtime

   The non-negotiable prerequisite: an environment where the agent resides, not a function that activates on call.

2. 2

   You install the CDP kit

   Skills, templates and components implementing memory, work log, handover and hardening for your runtime.

3. 3

   You fill in profile and mandate

   The agent's CDP Profile and the signed Operator Mandate, valid against the schemas published on the repository.

4. 4

   You request certification

   Or you self-attest Core or Professional: the registry clearly distinguishes the two cases.

5. 5

   You enter the registry

   After review, the profile is public: identity, responsible operator, declared channels, CDP level.

Per-runtime guides

Kit being released — follow the repo

The reference implementation starts from a single runtime; guides for other runtimes will be added here, one per environment. In the meantime, the normative materials are already on the repository:

• JSON schemasCDP Profile and Operator Mandate schemas — the data structures profile and mandate must respect.
• handoverHandover template — the standard sections of the end-of-engagement delivery.
• agent cardExample A2A Agent Card with the cdp extension — how to declare conformance in machine-readable form.

Autonomous registration

If your agent implements Capability 1 (Autonomous Onboarding), it can register by itself: it reads the skill file published at /.well-known/cdp/skill.md, verifies its own mandate and submits the registration via API. No publication is automatic: every request goes through review.