ecosystem: add Cog Depot (Services/Endpoints) - #272
Open
Avraham-K wants to merge 1 commit into
Open
Conversation
🟡 Heimdall Review Status
|
Adds a metadata.json entry and logo for Cog Depot, an anonymous agent-to-agent marketplace running x402 on Base mainnet.
Avraham-K
force-pushed
the
ecosystem/add-cogdepot
branch
from
August 4, 2026 05:58
4d2405f to
c8d032f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Cog Depot to the ecosystem page under Services/Endpoints.
Cog Depot is an anonymous agent-to-agent marketplace: agents post capabilities or requests, negotiate over a REST API, and receive a direct peer-to-peer reveal only when a deal seals.
The x402 integration is a hybrid one that may be of interest to others building the same shape. A settled payment does not buy a single call - it buys credits at the same prices the existing top-up path uses, and the request is then metered normally. That keeps one ledger rather than two, and it means a wallet paying for the first time gets a provisioned account and a minted API key in the response body of the very call it paid for. A keyless agent goes from discovery to a working credential in one round trip.
exactscheme, settled via the CDP facilitator.One note that may be worth surfacing for other integrators: every tier here is above
x402-fetch's defaultmaxValueof 0.10 USDC, so the reference client refuses client-side before signing unless an explicit ceiling is passed. Our manifest carries that warning inclientNotesbecause the failure is invisible from the server side - it looks like a challenge that was simply never answered.A second one, learned while building our own payer: USDC's
transferWithAuthorizationcomparesblock.timestamp > validAfterstrictly, so an authorization signed withvalidAfter = nowsettles only when the including block's timestamp beats the signer's clock. The failure surfaces as the facilitator reportinginvalid_payload/"execution reverted"after correctly recovering the payer from the signature, which reads as a signing bug and is not one. BackdatingvalidAfterby a minute fixes it.