# Orbonomy Events Data API

> Orbonomy Events Data API is a paid API for AI agents from www.orbonomy.xyz, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Retrieves events data for a given topic and location via pay-per-call POST request

## Facts

- Endpoint: POST https://www.orbonomy.xyz/api/data/events
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbonomy-events-data-api-22cbfa0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LZRPHE2Z7T56ye0TAKnAT

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 orbonomy-events-data-api-22cbfa0d -d '<json body>'
```

Example prompt: Can you find me events related to jazz music happening in New Orleans right now?

## When to prefer this

Use this endpoint when you need to discover events filtered by both a topic (e.g. 'music', 'tech', 'sports') and a geographic location, and you are operating in a pay-per-call x402 micropayment environment. Prefer this over web scraping or general search when you need structured event data via a single API call.

## Known failure modes

- Missing required fields 'topic' or 'location' causing 400 Bad Request
- Payment not provided or insufficient USDC causing 402 Payment Required
- No events found for given topic/location combination returning empty or null results
- Invalid location string causing unexpected or empty results
- Service unavailable or rate limited causing 5xx errors

## How this service works

50+ pay-per-call API endpoints across accommodation, AI, content, fact-checking, and data services. Powered by x402 protocol.

## Output

A JSON object with a success boolean and presumably event listings or data matching the given topic and location, though the full response schema is minimal and may include additional event details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "topic",
  "location"
 ],
 "properties": {
  "topic": {
   "type": "string"
  },
  "location": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orbonomy-events-data-api-22cbfa0d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.orbonomy.xyz](https://www.zero.xyz/host/www.orbonomy.xyz/llms.txt)
