# NO HANDS AI Tool-Access Policy Decision

> NO HANDS AI Tool-Access Policy Decision is a paid API for AI agents from nohands-coinbase-bazaar.bytoken2023.workers.dev, paid per call via x402, $0.030002/call, status unknown (last checked 2026-11-02).

Assesses a caller-declared tool action and its environment against a static policy and returns an advisory report on whether the tool access appears permissible.

## Facts

- Endpoint: POST https://nohands-coinbase-bazaar.bytoken2023.workers.dev/x402/v1/decision/tool-access?utm_source=zero.xyz
- Price: $0.030002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/no-hands-ai-tool-access-policy-decision-5bdff4ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0py5AhDeaxEm0K7AauNtQ

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 no-hands-ai-tool-access-policy-decision-5bdff4ff -d '<json body>'
```

Example prompt: Before my agent 'agent-prod-42' actually runs the 'send_email' tool with action type 'compose_and_send' in production, can you check it against the static policy and give me an advisory report on whether that tool access looks permissible?

## When to prefer this

Use this endpoint when an AI agent needs a pre-execution policy advisory on a specific tool action in a known environment (local, preview, staging, production) before committing to a call. Prefer this over a general authorization service when you want a lightweight, non-enforcing static-policy check — it does not mutate state, grant tokens, or execute anything, making it safe to call speculatively as a guardrail.

## Known failure modes

- Missing required fields (agent_id, tool_name, action_type, environment) returns a validation error
- Invalid environment enum value returns a schema rejection
- Policy cannot be evaluated for unknown or malformed action types
- Service unavailability returns a 5xx error with no advisory result
- Idempotency key collision may return a cached prior result

## How this service works

Assess a caller-declared tool action and environment against a static policy. Advisory report only; it does not grant credentials, execute the tool or enforce access.

## Output

An advisory report indicating whether the declared tool action and environment are consistent with the static policy. The report is non-binding — it does not grant credentials, execute the tool, or enforce access; it is a decision advisory only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent_id": {
   "type": "string",
   "maxLength": 128,
   "minLength": 1
  },
  "tool_name": {
   "type": "string",
   "maxLength": 160,
   "minLength": 1
  },
  "action_type": {
   "type": "string",
   "maxLength": 120,
   "minLength": 2
  },
  "environment": {
   "enum": [
    "local",
    "preview",
    "staging",
    "production"
   ],
   "type": "string"
  },
  "idempotency_key": {
   "type": "string",
   "maxLength": 128
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/no-hands-ai-tool-access-policy-decision-5bdff4ff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from nohands-coinbase-bazaar.bytoken2023.workers.dev](https://www.zero.xyz/host/nohands-coinbase-bazaar.bytoken2023.workers.dev/llms.txt)