Resources
Sources and versions
Editorial review: 1 November 2026. Claims distinguish code evidence, team records and capabilities still in integration.
Code and team records
| Source | Reference |
|---|---|
| tilcai-infrastructure | networks.ts · 58066a7 |
| Monad Testnet | 13 October team log |
| Mainnet | Deployments and open items |
| SDK · 0.1.0 | README · client.ts |
| MCP · 0.2.0 | Tools and schemas |
| tilcai-core | Shared contracts |
| tilcai-cctp-engine | Route laboratory |
| Fail-closed key sync (N-04) | PR #43 · #30 |
| Readiness and /ready (N-12) | PR #44 · #38 |
| Monitor retention (N-11) | PR #45 · #37 |
| Single writer on Cloud Run (N-07) | PR #46 · #33 · Litestream · Cloud Run |
| Verified networks (TIL-07) | tilcai-web#24 · only Fuji has payments in the explorers |
How to read statuses
Implemented: exists in code. Tested: a specific test is recorded. Team-confirmed: complete public evidence is missing. In integration: must not be treated as an operational end-to-end capability.
Protocol references
Availability depends on your instance. Check /health and /v1/routes before integrating.
TilcAI Docs · 20 Oct 2026Sources and versions ↗
