# parseapi.info Search Structures

> parseapi.info Search Structures is a paid API for AI agents from parseapi.info, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-16).

Search across previously parsed document structures stored in tenant memory

## Facts

- Endpoint: POST https://parseapi.info/search?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/parseapi-info-search-structures-f3cddc5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hl6nWH7amd_jxhU-yE6do

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 parseapi-info-search-structures-f3cddc5b -d '<json body>'
```

Example prompt: Search through all the parsed documents in my tenant memory for anything mentioning 'quarterly revenue targets' and return the matching structures.

## When to prefer this

Choose this endpoint when you need to search across documents that have already been parsed and stored in parseapi.info tenant memory. It is the right choice when you want to find specific content, clauses, or data points across a corpus of previously processed files (PDFs, DOCX, etc.) without re-parsing them. Prefer this over re-submitting documents to the parse endpoint when the content is already in memory.

## Known failure modes

- No matching results found for query — empty result set returned
- Tenant memory is empty or no documents have been parsed yet — returns empty or error
- Malformed request body — 400 error if required fields are missing
- Unauthorized access if tenant credentials are invalid
- Search query too vague resulting in noisy or irrelevant matches

## How this service works

Search structures

## Output

Returns matching document structures from the tenant's parsed document memory — likely including document identifiers, matched segments or blocks, and the structured content that satisfies the search query.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "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/parseapi-info-search-structures-f3cddc5b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from parseapi.info](https://www.zero.xyz/host/parseapi.info/llms.txt)