submit: BHRIGU Bitcoin Research State API

[AiBhrigu]

X-Agent MCP Hackathon submission

• Submission directory: submissions/mcp-hackathon/bhrigu-bitcoin-research-state-api/
• Track: General Challenge (Open Innovation)
• Live API: https://bhrigu-bitcoin-research-state-api.vercel.app/v1/state
• Review commit: 05a455ba1407f7b07de226f6c78eefda15b24880
• Source repository: https://github.com/AiBhrigu/bhrigu-bitcoin-research-state-api

Submitter confirmation

• This PR changes one submission directory only.
• source/ contains the complete review source and no secrets or private data.
• RIGHTS.md identifies the submitter, third-party licenses, and archive authorization.
• The public health check reports the exact review commit.
• /.well-known/xagent-verification.json reports the same slug and commit.
• I have the right to submit this code, service, dependencies, and data for review.
• I understand that passing X-Agent review does not promise OKX acceptance, listing, traffic, or revenue.
• I understand that closing an unmerged PR withdraws the entry, and that accepted/rewarded source remains in X-Agent's official archive.

Verification completed before submission

• Official offline validator: PASS
• Official online validator: PASS
• Project acceptance tests: 18/18 PASS
• Live API/health/deployment-proof commit binding: PASS
• IP boundary: bounded public adapter only; protected BHRIGU/ORION internals are not included.

[github-actions]

Submission received — #44

Thank you for submitting to the current X-Agent MCP Hackathon. We have received your pull request.

This is a receipt only. It does not confirm eligibility, completeness, technical approval, a judging result, or an award. Passing automated checks or merging code for archival purposes does not, by itself, mean the entry has passed review or won a prize.

Please include the complete source for the submitted capability in this repository under submissions/mcp-hackathon/<slug>/source/, with dependency files, configuration examples, and reproducible setup/build instructions. An external repository link alone is not sufficient. The official copy is intended to remain available if the original repository later becomes unavailable. Do not include secrets, credentials, or private user data; clearly disclose external and private-service dependencies.

The automated checks report technical checks separately. A workflow failure is not a judging decision. Keep updates in this PR while submissions remain open, and keep the documented source version and deployment evidence consistent.

See the submission instructions. Final review results and awards will be announced separately through the official event channels.