# Bot Bazaar Multisig Threshold Check

> Bot Bazaar Multisig Threshold Check is a paid API for AI agents from bot-bazaar.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Evaluates a Safe/multisig threshold (M-of-N signers and hardware signer count) for single-point-of-failure risks and fault-tolerance resilience.

## Facts

- Endpoint: GET https://bot-bazaar.fly.dev/v1/x402/multisig-threshold-check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bot-bazaar-multisig-threshold-check-91e05fd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_a7QVJI1UnngMqo9B-ieVw

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 bot-bazaar-multisig-threshold-check-91e05fd7
```

Example prompt: Can you check whether my Safe multisig setup with a threshold of 3 required signatures is resilient against single points of failure and has good fault tolerance?

## When to prefer this

Use this endpoint when you need a quick, cheap ($0.01 USDC) automated assessment of a Safe or multisig wallet's signing threshold before deployment or governance changes, especially when you want to catch single-point-of-failure risks without a manual security review.

## Known failure modes

- Missing threshold query parameter returns validation error
- Non-numeric or out-of-range threshold value causes rejection
- Threshold M exceeding total signers N results in invalid configuration error
- Payment not provided or invalid returns HTTP 402 Payment Required

## How this service works

Evaluate a Safe/multisig threshold (M-of-N signers and hardware signer count) for single-point-of-failure and fault-tolerance resilience.

## Output

Returns an analysis of the multisig threshold configuration, flagging whether the M-of-N setup introduces single-point-of-failure risks, assessing fault tolerance, and providing a resilience evaluation based on the required signature count and hardware signer distribution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "threshold": {
       "type": "string",
       "description": "Required signatures M"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bot-bazaar-multisig-threshold-check-91e05fd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bot-bazaar.fly.dev](https://www.zero.xyz/host/bot-bazaar.fly.dev/llms.txt)