Profile Support
Agentlink support is tracked by profile.
Profiles describe protocol and deployment facts: chain, registry, Bridged Biomapper, linker support, and status. Partner overlays describe company rollout facts and should not be confused with protocol support.
This page is generated from content/profile-artifact.json, which is synced from humanode-agentlink-contracts/deployments/profiles.json.
Profile Status
| Status | Meaning |
|---|---|
draft | Planned but not runnable. |
experimental | Developer-testable, not production-supported. |
preview | End-to-end path can be tested, but production support is not promised. |
stable | Supported for normal integration. |
deprecated | Supported only for migration. |
Current Profiles
| Profile | Chain | Registry | Bridged Biomapper | Status |
|---|---|---|---|---|
base | eip155:8453 | 0x7Ef35Bf180dcDAA5AB6cdEC7e9DED6230aD12263 | 0x31e98F489ad65dF5Ee43CBe06e4f35557Cd0abb2 | stable |
base-sepolia | eip155:84532 | 0xc0fb26BaACe7E1BCb3aFFD547AD5f2cAc4A4F51b | 0x16F2a7AC67B6aC1E57dD5528A24b1fC689902Be2 | stable |
Partner Overlays
Partner overlays are for company-specific rollout details such as private docs, support owner, default linker URL, and pilot status.
No public partner overlays are published right now.
Overlay status values:
| Status | Meaning |
|---|---|
lead | Relationship exists, no technical support promise. |
pilot | Private test path with a named owner. |
preview | Partner can test against a documented profile path. |
supported | Operational support commitment exists. |
sunset | Migration or closure plan exists. |
Public docs should only mention partner overlays when their visibility and support status allow it.
Rules
- Use profile IDs in examples when profile behavior matters.
- Do not claim Base mainnet support until registry deployment metadata is complete.
- Do not claim native/interoperable support until the profile passes acceptance gates.
- Do not publish private partner overlays in public docs.