# Apiosk Gateway – Company Identity Execute

> Apiosk Gateway – Company Identity Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.06/call, status unknown (last checked 2026-09-13).

Executes a company identity lookup operation via the Apiosk pay-per-call x402 gateway, returning structured business identity data for a given company.

## Facts

- Endpoint: POST https://gateway.apiosk.com/company-identity/execute
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-company-identity-execute-5c4e5c8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aRZS7k2FL54Je6JRxJD4x

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-company-identity-execute-5c4e5c8a -d '<json body>'
```

Example prompt: Look up the official identity information for Acme Corp — I need their registered name, country, and any other identity details you can find — use the company-identity operation via the Apiosk gateway.

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-use access to company identity data without a direct subscription to an identity data provider. It is ideal for sporadic lookups where a flat per-call USDC fee is preferable to a monthly API subscription, and when operating within an x402-compatible agent payment flow on Base.

## Known failure modes

- Invalid or unknown operation selector returns an error status
- Malformed JSON input payload causes upstream rejection
- Company not found in the underlying identity database returns empty or 404 upstream_status
- Insufficient USDC balance triggers HTTP 402 payment required
- Gateway timeout if upstream identity provider is slow or unavailable
- Misspelled company name yields no results or incorrect match

## 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 the upstream company identity response body, the operation used, HTTP status from the upstream API, latency in milliseconds, and the cost of the call in USDC. The 'result' field holds the raw company identity data such as registered name, jurisdiction, and other identity attributes returned by the underlying provider.

## 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-company-identity-execute-5c4e5c8a/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)