# Apiosk Gateway – Prospect Research Execution

> Apiosk Gateway – Prospect Research Execution is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-14).

Executes prospect research operations against the prospect-research API via the Apiosk x402 pay-per-call gateway, returning structured data about people or companies for sales and business development use cases.

## Facts

- Endpoint: POST https://gateway.apiosk.com/prospect-research/execute
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-prospect-research-execution-6f93cc4e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pfw1Kc66KL-6SSXhYwVom

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 apiosk-gateway-prospect-research-execution-6f93cc4e -d '<json body>'
```

Example prompt: Can you pull up prospect research on Acme Corp — I need their company profile, key decision makers, and any available contact info before my sales call tomorrow?

## When to prefer this

Choose this endpoint when you need pay-per-call prospect or lead research without a subscription commitment, and when you want a single gateway interface that handles payment via USDC on Base (x402 protocol). It is well-suited for agents that need on-demand sales intelligence enrichment without managing multiple API keys or billing relationships.

## Known failure modes

- Invalid or unrecognized operation selector returns an error status
- Malformed JSON input payload causes upstream rejection
- Prospect or company not found in underlying data source returns empty or null result
- Payment failure (insufficient USDC balance or x402 protocol error) blocks execution
- Upstream provider timeout results in elevated latency or error response
- Rate limiting by the upstream data provider

## How this service works

Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.

## Output

Returns a JSON object containing a status field, the upstream prospect research result (company profiles, people data, contact info, firmographics, or other structured intelligence depending on the operation), plus metadata including the API slug, operation selected, latency in milliseconds, cost incurred, and the upstream HTTP status code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "JSON payload forwarded to the selected operation."
  },
  "operation": {
   "type": "string",
   "description": "Operation id, /path, or METHOD /path selector."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "result"
 ],
 "properties": {
  "api": {
   "type": "string"
  },
  "cost": {
   "type": "string"
  },
  "result": {
   "description": "Upstream response body."
  },
  "status": {
   "type": "string"
  },
  "latency": {
   "type": "number"
  },
  "operation": {
   "type": "string"
  },
  "upstream_status": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-gateway-prospect-research-execution-6f93cc4e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)