# ISHOB Full-Text & Technical Specification Search

> ISHOB Full-Text & Technical Specification Search is a paid API for AI agents from api.ishob.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-14).

Performs full-text and technical specification search over ISHOB's licensed archive of documents and specifications

## Facts

- Endpoint: POST https://api.ishob.com/v1/search?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ishob-full-text-technical-specification-search-c8a68d01
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xz2SKk9OSzsplCsx5Y3Ij

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 ishob-full-text-technical-specification-search-c8a68d01 -d '<json body>'
```

Example prompt: Search the ISHOB licensed archive for all technical specifications related to 'IEEE 802.11 wireless communication standards' and return the top matching documents.

## When to prefer this

Choose this endpoint when you need to search a curated, licensed archive of technical specifications and full-text documents — especially for engineering standards, formal specs, or regulated technical content. Prefer this over generic web search when precision over a vetted licensed corpus is required and micropayment-per-query (x402) is acceptable.

## Known failure modes

- Empty results array if no documents match the query
- Authentication or payment failure (HTTP 402) if x402 micropayment is not properly handled
- Malformed request body returns validation error
- Rate limiting or quota exceeded errors
- Overly broad or ambiguous queries returning low-relevance results

## How this service works

Full-text + technical specification search over the licensed archive

## Output

Returns a list of search results from the licensed archive, typically including matching document titles, snippets, specification identifiers, and relevance metadata. The response is a JSON object with a 'results' array containing matched records.

## 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"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "results": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ishob-full-text-technical-specification-search-c8a68d01/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.ishob.com](https://www.zero.xyz/host/api.ishob.com/llms.txt)