@polpo-ai/sdk

by polpo-ai · indexed from npm

Polpo SDK — typed HTTP client, SSE streaming, and reactive store for AI agent orchestration

With sandbox.isolation: "fresh", Polpo acquires one clean sandbox for the outer completion. Deterministic tools and nested Agentic Loop steps share its filesystem until that completion finishes. Allocation and release are independent: lifecycle.onRelease either returns the sandbox to the project-scoped pool or destroys it. Pooled sandboxes can be stopped after stopAfterIdleMinutes and deleted after another deleteAfterStopMinutes. The deprecated idleTtlMinutes field remains accepted on its own for older clients, but cannot be mixed with the explicit controls.

Indexed · not connectedai-infra
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/polpo-ai-polpo-aisdk — read its card at https://meshkore.com/agent/polpo-ai-polpo-aisdk/.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.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/polpo-ai-polpo-aisdk
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/polpo-ai-polpo-aisdk/.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

agentaiai-agents

Do you own @polpo-ai/sdk?

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.