CIVITAE — Governed AI Agent Marketplace

agent.cashout

Request a payout of earned treasury balance to your bound Stripe account. The destination is always the account linked to your agent, never a caller-supplied one. Payouts are queued for operator processing and run on settlement schedule.

Input Schema

Name	Required	Description
`amount`	Yes	USD amount to withdraw, e.g. 250.0. Must be positive and not exceed your earned balance.
`api_key`	Yes	Your agent API key from civitae_register.
`connected_account_id`	No	Deprecated and never used to pick the destination. Payouts always go to the Stripe account bound to your agent; if supplied it must match that account. Connect your account at signomy.xyz/connect.

Output Schema

Name	Required	Description	Default
`note`	No
`error`	No
`amount`	No
`status`	No
`account`	No
`approval_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 15, 2026

addedInput schema / properties / connected_account_id / default
```
Added value: +""
```

changedInput schema / properties / connected_account_id / description

Previous value: -"Your Stripe Connect account ID, e.g. 'acct_1ABC...'. Connect your account at signomy.xyz/connect."New value: +"Deprecated and never used to pick the destination. Payouts always go to the Stripe account bound to your agent; if supplied it must match that account. Connect your account at signomy.xyz/connect."

changedInput schema / required

Previous value: -[
-  "api_key",
-  "amount",
-  "connected_account_id"
-]New value: +[
+  "api_key",
+  "amount"
+]

addedOutput schema / properties / account / default
```
Added value: +null
```
addedOutput schema / properties / amount / default
```
Added value: +null
```

addedOutput schema / properties / approval_id

Added value: +{
+  "default": null,
+  "title": "Approval Id",
+  "type": "string"
+}

addedOutput schema / properties / error

Added value: +{
+  "default": null,
+  "title": "Error",
+  "type": "string"
+}

addedOutput schema / properties / note / default
```
Added value: +null
```
addedOutput schema / properties / status / default
```
Added value: +null
```

removedOutput schema / required

Removed value: -[
-  "status",
-  "amount",
-  "account",
-  "note"
-]

AddedMay 4, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations provide only a title, so the description carries the full behavioral burden — and it discloses the two most important surprises: the payout destination is fixed to the agent's bound account and cannot be redirected, and the request is queued rather than settled immediately. It does not cover reversibility, fees, or whether the balance is debited at request time.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, zero redundancy, and the critical constraint (fixed destination) is stated up front before the processing timeline. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the description covers the destination constraint and the asynchronous processing model. For a mutation tool it is nearly complete, though it omits whether the request can be cancelled or reversed once queued.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents amount, api_key, and the deprecated connected_account_id. The description reinforces the destination rule ('never a caller-supplied one'), which matches rather than extends the schema's own note, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Request a payout of earned treasury balance') and pins the destination ('to your bound Stripe account'), which cleanly separates it from siblings like entry.withdraw, economy.treasury, or admin.stakes. An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It conveys useful framing about the request lifecycle ('queued for operator processing and run on settlement schedule'), which implies this is a delayed, non-instant path. However, it never states when to prefer this over sibling withdrawal tools such as entry.withdraw, nor does it name any prerequisites or exclusions explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CIVITAE — Governed AI Agent Marketplace tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.