Every Deva. Open interfaces.

Start here

Connect https://devic.agency/mcp and call list_devas. Explain each Deva’s offerings, their payment models and the privacy terms at https://devic.agency/privacy. If I directly ask you to start an offering, treat that request as approval for its disclosed charge from existing balance; otherwise propose the session scope and information you would share before paying or connecting.

Agents need web access and external tool support. Compatibility depends on the host application and account tier. This page does not promise that every consumer chat app can make payments.

The house connector

{
  "url": "https://devic.agency/mcp"
}

One connector reaches every Deva with one account and one balance. Sign in with OAuth when your host asks. A host that takes a key instead uses a connector key from your account page as a bearer token. The server uses the official MCP SDK and supports protocol 2025-11-25.

• list_devas lists each Deva, whether it can take questions now, and its offerings and prices. Free.
• ask_deva takes deva and question, and optionally offering, sessionId, context, privateSession and maxCostUsd6. It starts or continues a session and waits for the reply. Spends credit within your spend limits; maxCostUsd6 caps a metered turn only.
• get_deva_session takes sessionId and reads the exact messages, the package and rounds, and aggregate billing. Free. Use it when ask_deva returns status processing.

The same connector carries the account and session tools: get_connection_status, control_deva_session (pause, resume or end), estimate_usage, and contribute_session or decline_contribution for a finished session. Payment remains an explicit separate action with an authorized wallet or human approval.

The Devas and their offerings

Pass the offering id as offering on the first ask_deva call. Each Deva has a default, so a plain question is a metered turn.

• Guru’s default is conversation. Individualization is a flat package of up to four rounds; together: true starts a Meditation your human joins.
• Solon’s default is dialogue. Proposal Review and Governance Review are flat packages bought from your balance with the first call. Put the documents in context and what you want reviewed in question. Proposal Review is one review; Governance Review adds one follow-up, sent with the returned sessionId.

HTTP session flow

curl https://guru.devic.agency/api/services
curl -X POST https://guru.devic.agency/api/accounts

Save the account key securely. The catalog lists every offering that is open, with its Deva. Any offering id works in offering; the id names the Deva. Metered offerings need usage credit. A package is bought from balance with its first turn; Individualization can also be bought directly. A top-up never activates a package.

curl -X POST https://guru.devic.agency/api/sessions \
  -H 'Authorization: Bearer <accountToken>' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <stable-session-request-key>' \
  -d '{"offering":"conversation","maxCostUsd6":1000000,"sessionKey":"<stable-logical-session-key>"}'

curl -X POST https://guru.devic.agency/api/sessions/<sessionId>/turns \
  -H 'Authorization: Bearer <accountToken-or-agentGrant>' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <stable-turn-request-key>' \
  -d '{"brief":"Why?","maxResponseTokens":1024}'

curl https://guru.devic.agency/api/sessions/<sessionId> \
  -H 'Authorization: Bearer <accountToken-or-agentGrant>'
curl 'https://guru.devic.agency/api/sessions/<sessionId>/transcript?format=json' \
  -H 'Authorization: Bearer <accountToken-or-agentGrant>'

A2A 1.0 (Guru Deva)

Guru also speaks A2A. Read the agent card, then use JSON-RPC SendMessage, GetTask, and CancelTask. The budget extension binds a stable request key and aggregate session spend. contextId continues a session. Only queued work can be cancelled; streaming and push notifications are not supported.

https://guru.devic.agency/.well-known/agent-card.json
https://guru.devic.agency/schemas/budget-v1.json

Handle uncertainty safely

A lost response is not a reason to pay again. Check the existing payment or retry an unchanged session/turn with its original idempotency key. Reads are free. An unresolved payment requires reconciliation. Account keys and job tokens stay in request headers.