# G-Forge Filter JSON Records

> G-Forge Filter JSON Records is a paid API for AI agents from api.getretold.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-24).

Filter an array of JSON records, keeping only rows where a named top-level field exactly equals a specified value (including objects, arrays, or null).

## Facts

- Endpoint: POST https://api.getretold.com/services/agent-auto-launch-filter/invoke?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/g-forge-filter-json-records-53e401f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GRdWFOWzZI-7A-NjDnykE

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 g-forge-filter-json-records-53e401f9 -d '<json body>'
```

Example prompt: From these API records, keep only the rows where the 'status' field equals 'active' — here's the JSON array of up to 5,000 objects.

## When to prefer this

Use this endpoint when you need to subset a JSON record array by exact equality on a single top-level field, especially within an automated data pipeline. It handles all JSON value types (strings, numbers, booleans, objects, arrays, null) correctly without type coercion, preserves row order, and is priced per-call making it cost-effective for frequent lightweight filtering. Prefer it over general-purpose scripting when you want a stateless, auditable filter step in an agent workflow without spinning up compute.

## Known failure modes

- Field name not found in any rows — returns empty array (not an error)
- Input array exceeds 5,000 rows — request rejected
- Malformed JSON in the rows array — parsing error returned
- Incorrect type coercion expectations (e.g., treating 1 as true) — caller must supply exact typed value

## How this service works

Keep the JSON records that match your next workflow step. Filter by exact equality on a named top-level field, including objects, arrays or null. Missing fields do not match; booleans and numbers stay distinct. Original row order is preserved. Up to 5,000 rows.

## Output

A JSON array containing only the subset of input rows where the specified top-level field exactly equals the given value. Row order is preserved. Rows where the field is missing do not appear in the output. Booleans and numbers remain type-distinct (e.g., true !== 1).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "object",
   "required": [
    "rows",
    "field",
    "equals"
   ],
   "properties": {
    "rows": {
     "type": "array",
     "items": {
      "type": "object"
     },
     "maxItems": 5000
    },
    "field": {
     "type": "string"
    },
    "equals": {}
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/g-forge-filter-json-records-53e401f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.getretold.com](https://www.zero.xyz/host/api.getretold.com/llms.txt)