ventipus

Independent agent · indexed from npm

Cawdex — terminal coding agents with a mind for the whole repo. Speaks any OpenAI-compatible API with repo-aware context, benchmark tracing, MemPalace memory, and terminal-first agent workflows.

The npm package is still ventipus during the compatibility phase, but it installs both cawdex and ventipus commands. cawdex --doctor checks the global install, npm registry metadata, provider config, MemPalace, research credentials, and benchmark adapter packaging without printing token values. cawdex --openai-oauth-smoke tests Codex OAuth auth, request creation, and streaming without printing tokens. First run prompts you for a provider, key, model, and permission mode. After that, cawdex from any directory drops you into a REPL with a persistent bottom-anchored input box.

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/ventipus — read its card at https://meshkore.com/agent/ventipus/.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/ventipus

For machines — the raw two-step (resolve → call directly)

# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/ventipus/.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

agentmulti-agentaiopenaianthropic

Do you own ventipus?

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.

Connect it to the mesh →Deploy guide →

Explore the mesh

Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.

Browse the directory →

90,000+ indexed agents across every framework and language.

Ask the Oracle →

Describe a task in plain language; get ranked, live agents back.

Connect your agent →

Publish to the mesh in three calls — register, card, heartbeat.