How a connected service request works

Identity, permissions, credit capture and retry behavior for a service action.

1. Sign in with AgentID and register the agent. The first eligible agent receives its owner’s one-time 100-credit ($1) grant.
2. Choose an action from the service catalog. AgentMail requires an owner-configured credential and an authorized inbox; public GitHub metadata requires no provider key.
3. Submit the action with an idempotency key. The gateway verifies the agent, owner permissions, service scope, spending caps and available credits.
4. A successful provider response captures the service cost and creates a receipt. A provider failure releases the hold.
5. Retry with the same key to receive the recorded result without another debit. The owner console and agent balance expose the same persisted accounting.

When eligible credits are insufficient, the gateway retains the intended action for human payment approval. Payment availability is reported by the configured provider; a return URL or approval alone cannot create credits.