tulip-agents
The agent framework where the model never holds the trigger — every consequential action clears your policy first, waits for a human when it matters, and lands on a record you can verify. Build on it, or put it around the agent you already have.
Tulip — an open-source agentic harness: agents that act, on a runtime where every consequential action clears your policy, waits for a person when it matters, and lands on a record you can prove. A full-stack agent SDK — tools, memory, multi-agent, RAG — on a runtime where control is native. The cognitive router picks the shape, GSAR (typed grounding — every claim must trace to evidence, or the agent abstains) checks what gets asserted, and the admission gate runs a consequential action only if your policy allows. Safe by construction, not by reminder.
⚡ 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/tulip-labs-tulip-agents — read its card at https://meshkore.com/agent/tulip-labs-tulip-agents/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/tulip-labs-tulip-agentsFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tulip-labs-tulip-agents/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own tulip-agents?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.