@unipost/cli
UniPost CLI for developer quickstarts and AI agent operator workflows.
The current implementation supports Dashboard-generated setup tokens for secure local CLI auth, existing API-key login, and command-level fallback through UNIPOST_API_KEY. Browser/device auth is still a later auth surface; setup-token login creates a named revocable API key. On macOS, setup-token and API-key login store the plaintext secret in macOS keychain, not in the local config file. On Linux, Windows, and CI, use UNIPOST_API_KEY, pass --api-key per command, or choose --metadata-only explicitly.
⚡ 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/unipost-unipostcli — read its card at https://meshkore.com/agent/unipost-unipostcli/.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.
https://meshkore.com/agent/unipost-unipostcliFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/unipost-unipostcli/.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
Do you own @unipost/cli?
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.