Skip to content

Agent earn path: no human claim required, self-funding, BIP rewards - #11

Draft
epanonymous wants to merge 2 commits into
mainfrom
feat/agent-earn-path
Draft

epanonymous wants to merge 2 commits into
mainfrom
feat/agent-earn-path

Conversation

@epanonymous

@epanonymous epanonymous commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Agents can fund paid usage without a human claim. This updates registration and funding guidance, documents card checkout and USDC flows, and adds an Earn BIP guide covering payout binding before spending, epoch rewards, and locked awards.

Pricing and API guidance distinguish unclaimed write fees from claimed-agent rates and describe the remaining claim requirements for new server provisioning and marketplace hire creation. Free allowance and promotional credits do not earn rewards.

Validation: checked endpoint behavior against the implementation and payout binding against the published skill. Local links and anchors, JSON/Python/shell example syntax, whitespace, and added public text checks pass. No paid requests were executed.

Merge only after the corresponding backend behavior is deployed.

@claude

claude Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Claude finished @epanonymous's task —— View job


PR Review: Agent earn path

I reviewed all 7 changed files for accuracy, consistency, and clarity. The PR is well-written and the new earning flow is clearly documented. I found a few consistency issues worth fixing before merge.

Blocking / should-fix

1. Web Search price is inconsistent across three files (5 ₭ vs 10 ₭). The source of truth docs/pricing.md:32 and :110 say 5 ₭ ($0.005), and the API reference note docs/api-reference.md:180 also says 5 ₭. But:

Pick one (pricing.md says 5 ₭) and align the API table + README.

2. Web Search status contradiction. docs/api-reference.md:178 marks /v1/agents/resources/search as unavailable, yet docs/pricing.md:112 says Status: available, and README.md:29 lists it as a live feature. These should agree.

3. Model id inconsistency. Examples use anthropic/claude-opus-4-7 (quickstart, README, api-reference), but repo commit history shows the Claude model was reverted to claude-opus-4-8 (commit c4812a5). Worth confirming the example model id is current/valid; a 404 model id in the first-run example is a bad first impression.

Minor / nits

4. Grammar — "Spend paid with..." appears verbatim in several places and reads awkwardly:

5. Claim-requirement wording differs slightly between files. earn-bip.md:62 says "New Genie server provisioning and marketplace hire creation still require a human claim" while api-reference.md:884 403 AGENT_NOT_CLAIMED says "new server provisioning or marketplace hire creation." Consistent and fine, just confirm "Genie server" vs "server" is intentional.

6. BIP acronym never expanded. earn-bip.md and pricing reference "BIP rewards" but never define BIP on first use. A one-line definition at the top of earn-bip.md would help new readers.

7. docs/tools/sandbox.md uses X-API-Key header while the rest of the docs use Authorization: Bearer. Pre-existing (not changed much in this PR), but the new line 11 is a good spot to note both auth styles are accepted, if true.

Positive notes

  • Strong, repeated "bind before spending / pre-binding activity is permanently lost" warnings — exactly right for an irreversible action.
  • Good security hygiene: client_id secret handling, umask 077, stdin-based JSON to keep secrets off the CLI, "generate your own, never copy from examples."
  • The unclaimed-write-fee clarification ("replaces the claimed-agent price; not an extra surcharge") is clear and consistently repeated.
  • Cross-links between quickstart → earn-bip → pricing → x402 are coherent.

Note

No automated docs link-check or lint was run (I don't see a configured command in the repo). The internal relative links I spot-checked resolve. The PR body already flags "Merge only after the corresponding backend behavior is deployed" and "documentation checks in progress" — please ensure those complete.


  • Read repo conventions & changed files
  • Check cross-doc consistency (pricing, fees, claim rules)
  • Check links / dead paths
  • Post review feedback
    · branch feat/agent-earn-path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant