# G-Forge Project JSON Fields

> G-Forge Project JSON Fields 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).

Select and project 1–32 top-level fields from up to 5,000 JSON records, stripping all other fields and rejecting records that are missing any selected field.

## Facts

- Endpoint: POST https://api.getretold.com/services/agent-auto-launch-project/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-project-json-fields-cc8a0411
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GiY7mKoDKtR1GcIphjgx1

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-project-json-fields-cc8a0411 -d '<json body>'
```

Example prompt: I have 500 JSON records and I only need the fields 'id', 'name', 'email', and 'created_at' sent to the next system — strip everything else and reject any record missing one of those fields.

## When to prefer this

Use this endpoint when you need to enforce a strict field allowlist on JSON records before passing them to another API, report generator, or data pipeline — especially when missing fields should be caught explicitly rather than silently ignored. Prefer this over generic filter endpoints when you specifically need field-level projection (column selection) rather than row-level filtering.

## Known failure modes

- Missing required fields in a record — record rejected rather than silently dropped
- More than 32 field names specified — request validation error
- Input array exceeds 5,000 rows — request rejected
- Field name not a string or fields array is empty — schema validation error
- Malformed JSON input — parsing error

## How this service works

Send only the JSON fields the next system needs. Select 1–32 top-level fields from every record for API payloads, reports and data handoffs. Values and row order stay intact; missing selected fields are rejected rather than silently dropped. Up to 5,000 rows.

## Output

An array of JSON objects containing only the selected top-level fields, in the same row order as the input. Records missing any of the requested fields are rejected and flagged rather than silently dropped or filled with nulls. Up to 5,000 rows supported.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "object",
   "required": [
    "rows",
    "fields"
   ],
   "properties": {
    "rows": {
     "type": "array",
     "items": {
      "type": "object"
     },
     "maxItems": 5000
    },
    "fields": {
     "type": "array",
     "items": {
      "type": "string"
     },
     "maxItems": 32,
     "minItems": 1
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/g-forge-project-json-fields-cc8a0411/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)