brc.dev valid
BRC
For agents: Index of BRC technical specifications for BSV wallet protocols, app messaging, proof formats and Metanet access gates; a reference for wallet developers.
bitcoin-svwallet-protocolsbrc-standardsmetanetspecifications
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T11:46:14.475Z. Cached copy · Source on brc.dev
# BRC
## BRC
- [README](https://bsv.brc.dev/readme.md)
- [Banana-Powered Bitcoin Wallet Control Protocol](https://bsv.brc.dev/example/example.md)
- [The deployment-info.json Specification](https://bsv.brc.dev/apps/0102.md)
- [Auditable Real-time Inference Architecture (ARIA)](https://bsv.brc.dev/apps/0122.md)
- [Registry-Free Typed Content Anchor with On-Chain Code Provenance](https://bsv.brc.dev/apps/0145.md)
- [Verifiable Time Allocation](https://bsv.brc.dev/apps/0168.md)
- [Locked Content Header (LCH) — Licensed, Micropayment-Enabled Content](https://bsv.brc.dev/apps/0170.md)
- [Access Gates for Metanet Rooms](https://bsv.brc.dev/apps/0190.md)
- [Application Output Knowledge and Source Adapters](https://bsv.brc.dev/apps/0192.md)
- [LCH Acquisition through Private Overlays and Listing Covenants](https://bsv.brc.dev/apps/0198.md)
- [Derived Collectibles](https://bsv.brc.dev/apps/0210.md)
- [Dead-Man Timed Reveal of a Sealed Secret](https://bsv.brc.dev/apps/0216.md)
- [Chat-Native Command Grammar for the Metanet](https://bsv.brc.dev/apps/0218.md)
- [NotaryHash — Privacy-Preserving Signed-Hash Notarization with SPV-Verifiable Certificates](https://bsv.brc.dev/apps/0220.md)
- [Consent Envelope: Verifiable Multi-Party Document Signing with On-Chain Signing Order](https://bsv.brc.dev/apps/0222.md)
- [Block Media Format (BMF) — Composable On-Chain Audio/Video](https://bsv.brc.dev/apps/0224.md)
- [Frictionless On-Chain Onboarding via Pre-Funded Claimable Tokens](https://bsv.brc.dev/apps/0227.md)
- [Transaction Creation](https://bsv.brc.dev/wallet/0001.md)
- [Data Encryption and Decryption](https://bsv.brc.dev/wallet/0002.md)
- [Digital Signature Creation and Verification](https://bsv.brc.dev/wallet/0003.md)
- [Input Redemption](https://bsv.brc.dev/wallet/0004.md)
- [HTTP Wallet Communications Substrate](https://bsv.brc.dev/wallet/0005.md)
- [XDM Wallet Communications Substrate](https://bsv.brc.dev/wallet/0006.md)
- [Window Wallet Communication Substrate](https://bsv.brc.dev/wallet/0007.md)
- [Wallet Transaction Output Tracking (Output Baskets)](https://bsv.brc.dev/wallet/0046.md)
- [Submitting Received Payments to a Wallet](https://bsv.brc.dev/wallet/0050.md)
- [Certificate Creation and Revelation](https://bsv.brc.dev/wallet/0053.md)
- [Unified Abstract Wallet-to-Application Messaging Layer](https://bsv.brc.dev/wallet/0056.md)
- [Transaction Labels and List Actions](https://bsv.brc.dev/wallet/0065.md)
- [Output Basket Removal and Certificate Deletion](https://bsv.brc.dev/wallet/0066.md)
- [Group Permissions for App Access](https://bsv.brc.dev/wallet/0073.md)
- [Extensible Proof-Type Format for Specific Key Linkage Claims](https://bsv.brc.dev/wallet/0097.md)
- [P Protocols: Allowing future wallet protocol permission schemes](https://bsv.brc.dev/wallet/0098.md)
- [P Baskets: Allowing Future Wallet Basket and Digital Asset Permission Schemes](https://bsv.brc.dev/wallet/0099.md)
- [Unified, Vendor-Neutral, Unchanging, and Open BSV Blockchain Standard Wal
…
Related sites
Find similar publishers by meaning →
Other listed sites in Documentation and reference. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ubuntu.com | Ubuntu | documentation Open source projects Infrastructure +1 | GB | 76 | ✓ | ✓ | |
| cpanel.net | cPanel & WHM Documentation | documentation Marketing Documentation and reference +1 | US | 73 | ✓ | ||
| openai.com | OpenAI Developers | interface Education Developer tools +3 | — | 72 | ✓ | ✓ | |
| nvidia.com | NVIDIA Corporation | documentation Developer tools AI and machine learning +1 | US | 71 | ✓ | ||
| adafruit.com | Adafruit Learning System | documentation Education Documentation and reference +1 | — | 70 | ✓ | ✓ | |
| gravatar.com | Gravatar API Documentation v3.0.0 – LLMS.TXT | interface APIs and SDKs Documentation and reference | US | 70 | ✓ | ||
| readthedocs.io | Your Documentation Infrastructure Layer | documentation Documentation and reference Developer tools | — | 70 | ✓ | ✓ | |
| zoom.com | Zoom Technical Library | interface Communications Documentation and reference | — | 70 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=brc.dev · GET /v1/domain/brc.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage brc.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for brc.dev:
1. POST https://agentwebmap.com/v1/sites/brc.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://brc.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/brc.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/brc.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.