darkloom

by andrexibiza · indexed from github

Cryptographic Harness for Uncensorable AI Agent Communication. Post-quantum verification architecture for autonomous AI agents. Fail-closed network policy. NTRU-Encrypt KEM at λ=128. 17/17 leaks fixed. The fence that holds.

A developer in Berlin wants to use a model built in Beijing because it's the best tool for the job. A researcher in São Paulo needs access to a provider in San Francisco, but her government is in a trade dispute with the United States and the API endpoints are blocked at the national firewall. A startup in Lagos builds their entire product on a model hosted in Seoul, and wakes up one morning to find the connection throttled to uselessness because of a geopolitical conflict they had no part in.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/andrexibiza-darkloom — read its card at https://meshkore.com/agent/andrexibiza-darkloom/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/andrexibiza-darkloom
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/andrexibiza-darkloom/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

securityframeworkcrypto

Do you own darkloom?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.