# Polyform Inbound Request Screen

> Polyform Inbound Request Screen is a paid API for AI agents from api.polyform.org, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-11).

Screens an inbound HTTP GET request for security risk and returns a verdict (e.g. CHALLENGE, ALLOW, BLOCK) with a numeric risk score

## Facts

- Endpoint: GET https://api.polyform.org/v1/security/inbound-request-screen?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/polyform-inbound-request-screen-b3b24faa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JoaqOEIbXl9ymcqE4eYls

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 polyform-inbound-request-screen-b3b24faa
```

Example prompt: Screen this inbound HTTP GET request for security risk and tell me whether to allow, challenge, or block it — I need the verdict and the risk score.

## When to prefer this

Use this endpoint when you need a fast, low-cost, per-call security verdict on individual inbound HTTP GET requests without maintaining an account or API key — ideal for agent-driven or serverless architectures that process requests on demand and need lightweight abuse/bot screening integrated into a micropayment workflow.

## Known failure modes

- Missing required 'input' object or 'type'/'method' fields returns a validation error
- Unsupported HTTP method (non-GET) in the method enum causes a schema rejection
- Payment failure or insufficient USDC balance blocks the call before screening occurs
- Malformed query parameters object may cause unexpected scoring behavior

## How this service works

Pay-per-call data endpoints for AI agents. USDC on Base via x402. No account, no API key — one micropayment per call.

## Output

Returns a JSON object with a 'verdict' field (e.g. 'CHALLENGE', 'ALLOW', 'BLOCK') and a numeric 'riskScore' (0–100) indicating the assessed threat level of the inbound request.

## 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"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "verdict": "CHALLENGE",
  "riskScore": 35
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/polyform-inbound-request-screen-b3b24faa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.polyform.org](https://www.zero.xyz/host/api.polyform.org/llms.txt)