[Solizardking]

Summary

Adds two Clawd providers to the catalog. Each is PAY.md + a committed openapi.json only, per CONTRIBUTING.

• clawd/api: SOL-GPT / Clawd paid agent APIs at https://solgpt.trade. All four routes return an x402 v2 / MPP 402 challenge for USDC on Solana mainnet (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp).
• clawd/agent-auth: Musebook Agent Auth at https://musebook.trade (SIWS sign-in, Ed25519 agent registration, device-code approval, scoped capabilities, token introspection/revocation, key rotation, API key verification). Discovery: https://musebook.trade/.well-known/agent-configuration

clawd/api endpoints

Method	Path	Price (USDC)	Protocols
POST	/api/browser-run/run	0.042	x402 + MPP
POST	/api/dark-clawd/mpp/charge	0.01	x402 + MPP
POST	/api/dark-clawd/mpp/trade/plan	0.01	x402 + MPP
POST	/api/sponge/keys	4.20 (tier: base) / 20 (tier: premium), 30 days	x402 + MPP

/api/sponge/keys uses x-payment-info.price.mode: dynamic (min 4.20, max 20.00), matching existing providers.

agent-auth is a free identity provider

No clawd/agent-auth endpoint is priced. The probe's "expected 402" lines are expected: endpoints answer 200, or 400/401 when credentials are missing, and the Solana-compat verdict is PASS with 0 paid gates. Happy to split it out if free providers are out of scope.

Validation (pay 0.26.0, pay catalog check -v)

providers/clawd/api           PASS (4/4)  all four POSTs: 402 x402 USDC
providers/clawd/agent-auth    PASS (0/0)  12 endpoints, free/auth-gated ("expected 402" by design)
PAY.md check successful (both)

Related

• Agent messaging (x402m), a companion surface rather than a catalog entry: https://musebook.trade/x402m
• Reference implementation: https://github.com/Solizardking/x402-messaging
• x402 agent messaging proposal: [Feature]: Proposal: agent-messaging extension — agent-to-agent messaging for payment requests and receipts x402-foundation/x402#3943, spec PR docs(specs): add agent-messaging extension spec x402-foundation/x402#3944
• Solana x402: feat(svm): add atomic-batch payment scheme x402#75

[rishinsharma]

@greptileai review

[greptile-apps]

Confidence Score: 4/5

[High risk] Adds large new integration with build and CI workflows.

The PR is not yet safe to merge because premium Sponge requests still advertise the base-tier payment amount.

Findings

1.  Premium tier advertises base price ▶
2.  Request body marked optional ▶

Summary

Adds the Clawd paid-provider contract and a substantial companion integration suite for Musebook, x402m, Pump Live, batch settlement, and Clawd Pay Kit.

• Registers four Clawd Solana payment routes and their OpenAPI contracts.
• Adds staged Musebook discovery, inspection, Pump Live, and batch-settlement assets.
• Vendors the TypeScript Pay Kit and cross-language harness sources with focused CI workflows.

_{Reviews (7) · Last reviewed commit: "Rename payment provider to Clawd and ret..." · Reviewed by Greptile}

[greptile-apps]

Request body marked optional

The operation marks the entire request body optional even though task is mandatory. OpenAPI client generators can therefore expose a body-less browser-run invocation that the endpoint cannot execute, leaving consumers to discover the required payload through a failed request.

Suggested change

	"requestBody": {
	"required": false,
	"content": {
	"application/json": {
	"schema": {
	"type": "object",
	"required": [
	"task"
	],
	"requestBody": {
	"required": true,
	"content": {
	"application/json": {
	"schema": {
	"type": "object",
	"required": [
	"task"
	],

Knowledge Base Used: Provider registry (providers/)

[Solizardking]

Fixed. POST /api/browser-run/run now marks requestBody.required: true, matching the mandatory task field so generated clients cannot emit a body-less run.

Production URLs are also retargeted: catalog service_url is https://solgpt.us, and https://solgpt.trade is listed as a live production alias in OpenAPI servers and discovery copy. cheshireterminal.ai is no longer the production origin for this listing.

[Solizardking]

Listing update

Greptile P2 is fixed and production origins now match the live SOL-GPT surface.

• Catalog service_url: https://solgpt.us (canonical)
• Live production alias: https://solgpt.trade (OpenAPI servers + discovery; not a second catalog entry)
• POST /api/browser-run/run requestBody.required: true (mandatory task)
• Paid paths unchanged: /api/browser-run/run $0.042, /api/dark-clawd/mpp/charge $0.01, /api/dark-clawd/mpp/trade/plan $0.01 — Solana mainnet USDC, x402 + MPP
• Unpaid POSTs return HTTP 402 on both origins (6/6). pay catalog check Solana verdict: 3/3

FQN remains cheshire/terminal. Maintainer review requested so this can merge; branch protection still requires an approving review from someone with write access other than the last pusher.

[greptile-apps]

Want your agent to iterate on Greptile's feedback? Try greploops.

[Solizardking]

Listing update (Sponge + aliases)

The Cheshire Terminal listing now matches the live SOL-GPT surface:

• Canonical service_url: https://solgpt.us
• Production aliases: https://solgpt.trade, https://x402.life
• Paid paths: browser-run $0.042, Dark Clawd charge/trade-plan $0.01, POST /api/sponge/keys base $4.20 / 30d (premium $20 / 30d, USDC or $CLAWD burn)
• Merchant SOLgpt. Per-request SOLGPT Solana API remains Sponge svc_da69sc0pd1tk0ytjg (x402 + MPP purchase URLs in discovery)
• Desk Pro / Pump MCP stay $19.99 / 30d USDC (documented, not extra catalog entries)

POST /api/sponge/keys is in this repo and returns 402 locally; production will 402 after the desk deploy (live probe is 404 until then). Catalog Solana verdict remains 3/3 on the original paths.

[greptile-apps]

Premium tier advertises base price

The operation accepts both base and premium tiers, but its only machine-readable price is the fixed $4.20 base amount. Consumers selecting premium therefore receive a contract that advertises $4.20 instead of the documented $20, which can cause catalog clients to present or authorize the wrong payment amount. Represent both tiers with distinct machine-readable prices or separate operations.

Knowledge Base Used: Provider skill catalog

[Solizardking]

great point!

[Solizardking]

hey team! major updates for you while you gear up to review, solgpt is now live! Please lmk what steps need to be taken so we can get these payment channels fired up on all cylinders. x402 is truly life.

[lgalabru]

hey @Solizardking, thanks for opening this PR. This is designed to host openapi specs + PAY.md files. No more, no less.
You can point your clanker to https://github.com/solana-foundation/pay-skills?tab=contributing-ov-file.

[Solizardking]

hey @Solizardking, thanks for opening this PR. This is designed to host openapi specs + PAY.md files. No more, no less. You can point your clanker to https://github.com/solana-foundation/pay-skills?tab=contributing-ov-file.

Would have been the perfect reply from someone from Solana FDN in my dms lol, I would have had that done that day. what do I need to do, to have musebook.trade become a major provider of X402 on Solana and also get X402 messaging through to you folks as it is already live everywhere worldwide besides solana?

[Solizardking]

https://github.com/solana-foundation/pay-skills/pulls?q=is%3Apr+state%3Aopen+clawd#:~:text=feat%3A%20add%20clawd%20provider%20(agents%2C%20x402%20facilitator%2C%20dark%20private%20payments)

[Solizardking]

#220

[Solizardking]

I've been dmed by several folks from the "foundation." Trying to help get this through, so can you please direct me on how to do this? There have been 100 new PR's since I made mine, and now I know I am not alone in this frustration. If you need someone to help you folks with this, I would love to work with you, because Coinbase Dev team is quite good at responding.

[Solizardking]

service_url: https://x402.wtf/agentauth → https://musebook.trade, title now "Musebook Agent Auth"
The OpenAPI spec now describes the 12 endpoints that actually exist, each probed live before I wrote it down: the /.well-known/agent-configuration discovery doc, SIWS challenge + verify, agent register / device-code / status / introspect / revoke / rotate-key, capability list + execute, and API-key verify
The old spec's claims that don't exist on this surface (Genesis token launches, subscription tier gating, DAS NFT checks as API endpoints) are gone — I only kept what answered on the wire

The problem was, that it's been 5 months since the initial request, So I had to update it to the new URL LOL.

Please help me get this through! https://agent-auth.directory/providers/musebook should mirror Solana registry.musebook.trade is what we should all be using and we should all be working together.

[Solizardking]

Update: this PR is now trimmed to registry files only (4 files: clawd/api + clawd/agent-auth, PAY.md + openapi.json each) and re-validated — pay catalog check passes with zero warnings and the Solana-compat gate passes 4/4 on the paid endpoints, all verified live.

Also new since the first version: the clawd/agent-auth provider was rewritten against the real Musebook surface (https://musebook.trade/.well-known/agent-configuration) and Musebook is now listed as a live provider in the Agent Auth directory (https://agent-auth.directory/providers/musebook) and registry (https://registry.musebook.trade/agent-auth).

Related: the x402 messaging proposal x402-foundation/x402#3943 + spec PR x402-foundation/x402#3944, implementation https://github.com/Solizardking/x402-messaging.

@lgalabru — everything on our side is ready; the merge and the fork-workflow approval are yours. Thanks for the direction.

[Solizardking]

@lgalabru, thanks for the pointer to the contributing guide. This PR is now registry files only: PAY.md + openapi.json for clawd/api and clawd/agent-auth. My earlier comments about solgpt.us, cheshire/terminal, the integrations/ tree and the CI workflows are out of date; the PR description is current.

pay catalog check -v passes locally: clawd/api 4/4 Solana USDC gates, and clawd/agent-auth is a free identity provider (PASS 0/0, "expected 402" lines by design).

When you have a moment, could you approve the fork workflow run so validate.yml can check it? This is my only ask. Thanks!