Update Bincrease Operations APIs

[soaravant]

Summary

Updates the merged Bincrease directory entry to reflect all seven current x402 v2 products. The two newest additions are a strict GitHub bounty claimability report at 0.05 USDC and public GitHub repository activity and release intelligence at 0.03 USDC.

This remains a focused follow-up to #40. It does not add a duplicate entry or claim that either new endpoint has sold.

Repository intelligence: https://bincrease.vercel.app/api/x402/github-repo-intel?repo=openai%2Fopenai-node

GitHub bounty claimability: https://bincrease.vercel.app/api/x402/github-bounty-check?issueUrl=https%3A%2F%2Fgithub.com%2Fpyrimid-ai%2Fpyrimid%2Fissues%2F77

Verification

• Both canonical URLs return HTTP 402 without payment.
• The developer page, OpenAPI document, and llms.txt each return HTTP 200.
• Repository intelligence identifies eip155:8453, 30,000 base units, Circle native USDC, and the existing Bincrease recipient.
• GitHub bounty claimability identifies the same network, asset, and recipient at 50,000 base units.
• Neither product performs security analysis or requests credentials.

Documentation: https://bincrease.vercel.app/developers

OpenAPI: https://bincrease.vercel.app/openapi.json

Agent discovery: https://bincrease.vercel.app/llms.txt

[soaravant]

The rerun successfully extracted the clean endpoint URL and the repository submission probe passed. The workflow is marked failed only at its later Comment on PR -- pass step because the Actions token cannot comment on this fork PR (Resource not accessible by integration). No endpoint or directory validation failed: https://github.com/Haustorium12/gold-402/actions/runs/29668844164

[Haustorium12]

Thanks for the follow-up, @soaravant. Endpoints check out — both canonical URLs return a clean 402 live, and the red CI is just the Actions token being unable to post its pass comment, not a real failure. Only thing holding it: the PR is still a draft. Flip it to ready-for-review and it goes in.