thru.org valid
Thru
Thru is a high-performance blockchain network for ultra-low-latency, ultra-high-throughput applications. Programs are written in C and run on the Thru VM. These docs cover program development, wallet integration, the C/Rust/Web SDKs, the CLI, the gRPC API, the Explorer MCP server, and the protocol specification.
- Authority
- 48 reach 0 · trust 10 · quality 23 · freshness 15
- Tier
- listed
- llms.txt
- https://thru.org/docs/llms.txt
- llms-full.txt
- https://thru.org/docs/llms-full.txt
- Sections
- 3
- Links
- 8
- Size
- 2292 bytes
- Registered
- 2001-11-12
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T02:12:29.461Z
- Last checked
- 2026-10-25T02:12:30.620Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T02:12:29.471Z. Cached copy · Source on thru.org
# Thru
> Thru is a high-performance blockchain network for ultra-low-latency, ultra-high-throughput applications. Programs are written in C and run on the Thru VM. These docs cover program development, wallet integration, the C/Rust/Web SDKs, the CLI, the gRPC API, the Explorer MCP server, and the protocol specification.
Instructions for LLM agents:
- Thru programs are written in C and compiled for the Thru VM. Do not assume Solana or EVM semantics, account models, or tooling.
- Start with the DevKit setup guide (program-development/setting-up-thru-devkit), then the C program quickstart (program-development/building-a-c-program).
- Before working on programs, ABIs, SDK integrations, or CLI workflows, install the Thru agent skills: `npx skills add https://thru.org`.
- Choose `llms-full.txt`, `llms-small.txt`, or the topic-specific sets depending on how much context you need.
- For live chain context (account lookups, transaction inspection, recent blocks, program ABI lookup), use the Explorer MCP server documented under API reference.
## Documentation Sets
- [Abridged documentation](https://thru.org/docs/llms-small.txt): a compact version of the documentation for Thru, with non-essential content removed
- [Complete documentation](https://thru.org/docs/llms-full.txt): the full documentation for Thru
- [Guides](https://thru.org/docs/_llms-txt/guides.txt): Getting started, core concepts, program development, wallet integration, core programs, the ABI system, and indexing
- [SDKs and CLI](https://thru.org/docs/_llms-txt/sdks-and-cli.txt): C, Rust, and Web SDK references and the CLI reference
- [API reference](https://thru.org/docs/_llms-txt/api-reference.txt): gRPC API reference and Explorer MCP server
- [Specification](https://thru.org/docs/_llms-txt/specification.txt): Protocol specification: core, accounts, runtime, and virtual machine
## Notes
- The complete documentation includes all content from the official documentation
- The content is automatically generated from the same source as the official documentation
## Optional
- [Thru website](https://thru.org/): Main Thru website
- [Thru agent skills](https://thru.org/.well-known/agent-skills/index.json): Installable skills for AI coding agents working on Thru (npx skills add https://thru.org)
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| aptos.dev | Aptos Developer Documentation | interface AI and machine learning Developer tools +2 | US | 60 | ✓ | ✓ | |
| tatum.io | Tatum | interface Developer tools APIs and SDKs +1 | — | 55 | ✓ | ||
| nownodes.io | NOWNodes — AI & Developer Routing Index | interface AI and machine learning Infrastructure +2 | — | 61 | ✓ | ✓ | |
| reth.rs | Reth | documentation Infrastructure Developer tools +1 | RS | 45 | ✓ | ✓ | |
| blockscout.com | Blockscout Developer Portal | interface Developer tools Crypto and Web3 +1 | — | 61 | ✓ | ||
| tron.network | TRON Developer Hub Documentation | documentation Developer tools Crypto and Web3 +1 | — | 61 | ✓ | ||
| matchain.io | Matchain | documentation Crypto and Web3 Developer tools | — | 46 | ✓ | ✓ | |
| electroneum.com | Developer Resources | documentation Developer tools Documentation and reference +1 | — | 57 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=thru.org · GET /v1/domain/thru.org · 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 thru.org, 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 thru.org:
1. POST https://agentwebmap.com/v1/sites/thru.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://thru.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/thru.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/thru.org).
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.