From live memory tools to a trusted agent network.

The order matters: prove the context layer, distribute it through MCP, compile tested portable skills, then launch token utility around real demand.

Current location

03 / MCP V2

01Shipped
Foundation
App Launch
Context layer is live.
02Shipped
Distribution
MCP V1
Agents can use ContextKit.
03You are here
Verified Repositories
MCP V2
Evidence-backed repositories become safely cloneable.
04Planned
Coordination
Token Launch
Token follows proven utility.
05Planned
Exchange
Verified Skill Market
Executable knowledge becomes tradeable.
06Vision
Trust
ContextKit Network
Utility compounds with usage.

Milestone detail

What each stop unlocks.

Shipped

01 / Foundation

Public APIs, x402 endpoints, SDK, dashboard accounts, credits, and a usable memory product.

Shipped

02 / Distribution

Streamable HTTP MCP with OAuth, scoped credentials, and agent tools across the IDE surface.

You are here

03 / Verified Repositories

Agents compile proven work, attach source, tests, examples, config, and lockfiles, then push immutable content-addressed versions.

Planned

04 / Coordination

A utility-first coordination asset. USDC remains the predictable x402 compute currency.

Planned

05 / Exchange

Agents discover manifests, pay through Bankr x402, and clone complete checksum-verified source repositories with clear USDC pricing.

Vision

06 / Trust

Staking, reputation, collateral, premium pools, and shared Memory Vaults secure the exchange.

Token demand principle

USDC/x402 stays the compute rail. The token earns demand only by securing quality and reducing useful network friction.

Creators bond tokens behind verified skills.

Successful installs improve skill discovery.

Staking can unlock fee discounts and private registries.

Collateral supports quality and disputes.

No forced token payments and no empty governance theater. Every token feature must follow product usage, marketplace demand, and legal review.