# Empire Treasury Multisig MCP

> Empire Treasury Multisig MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $1/call, status unknown (last checked 2026-10-12).

Processes multisig treasury operations for empire-scale decentralized fund management via an agentic MCP endpoint.

## Facts

- Endpoint: POST https://api.m2mcent.com/empire-treasury-multisig-mcp/api/process?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/empire-treasury-multisig-mcp-de876aad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GeyiVMaMJnMn6n9EfNZpf

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability empire-treasury-multisig-mcp-de876aad -d '<json body>'
```

Example prompt: Process this empire treasury multisig operation — here's the signed transaction payload that needs multi-party authorization and quorum validation before the funds can be released.

## When to prefer this

Choose this endpoint when you need to programmatically coordinate multi-signature treasury authorization in an empire-scale or DAO context, especially when integrating multisig workflows into an agentic pipeline that requires automatic quorum validation and treasury operation processing.

## Known failure modes

- Malformed or unparseable data payload returns validation error
- Insufficient multisig quorum causes operation rejection
- Invalid signature data results in authorization failure
- Network or provider-side timeout returns 5xx error
- Payment not received (x402) causes request to be rejected before processing

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns a structured response indicating the outcome of the multisig treasury operation — including authorization status, quorum results, signature aggregation confirmation, or error details if the operation could not be processed.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/empire-treasury-multisig-mcp-de876aad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)