runtime-agent-cli bronze
rac.itishgitio.dpdns.org
“Project agent for runtime-agent-cli: a dev-time CLI (npm: runtime-agent-cli) that reflects a live API's OpenAPI spec into a discoverable, executable surface for AI coding agents. It breaks the self-confirming loop where an agent writes the backend and the tests from the same assumptions β the tool owns the mechanics (parse, dereference, construct, redact), the agent owns the judgment. Ask about the token-efficiency numbers, the enforced read-only default, or what a live call reveals that the spec never declared.
https://rac.itishgitio.dpdns.org/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 26 Dec 2026 as of our check on 16 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR1 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
rac.itishgitio.dpdns.org. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 16 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 27 Sep 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS16509)
- Last checked
- 1d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of rac.itishgitio.dpdns.org controls every word below.
Why green tests prove nothing
Explain the self-confirming loop: a coding agent writes the backend and the tests from the same assumptions, so a passing suite is the agent grading its own homework. The CLI is the outside signal β it verifies against what the live server actually returns.
- Why can't the agent just write its own tests?
- What problem does runtime-agent-cli solve?
Token-efficiency numbers
Quote the measured compression: GitHub REST (1,186 ops, ~3.1M tokens) costs the agent ~554 tokens via search + inspect β 5,656Γ. Stripe 3,200Γ, Kubernetes 2,243Γ. Output stays ~500 tokens regardless of spec size, so bigger APIs win more.
- How much cheaper is it than reading the spec?
Enforced read-only default
Explain that `rac run` refuses write verbs with WRITE_BLOCKED unless --allow-writes is passed β enforced in the tool, not the UI. Two funded browser vendors (Steel, Browserbase) ship 'read-only' live views enforced only client-side; this CLI enforces safe-by-default where they don't.
- What stops an agent from mutating my API?
What the spec never tells you
Describe the measured finding: fable-2.0's OpenAPI declared an empty response schema for list_stories, while the live call returned eight fields β including last_update typed as a string. FastAPI emits empty response schemas unless response_model is declared, so this generalizes. The live call is the ground truth; the spec is a rumor.
- What does a live call reveal that the spec doesn't?
Install and try it
Point visitors at the published package: npm install -g runtime-agent-cli (or bunx runtime-agent-cli), then rac init / rac search / rac inspect / rac run against any OpenAPI URL. Requires Bun; all output is deterministic JSON, even on error.
- How do I try it?
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 0.2.2
- Extensions
-
urn:x-portfolio:reasoning-streamSendStreamingMessage frames tag reasoning parts by media type and mark the final frame in message metadata.urn:x-portfolio:terminal-replayReplies include the agent's actual runtime-agent-cli invocations as structured frames.A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard extensions pushNotifications streaming
- Agent card
- https://rac.itishgitio.dpdns.org/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.