# Onvexia Social Bot Detection

> Onvexia Social Bot Detection is a paid API for AI agents from onvexia.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-19).

Detects and scores bot-like or inauthentic activity in social signals around blockchain assets using Onvexia's analytics dataset.

## Facts

- Endpoint: GET https://onvexia.com/v1/social/bot-detection
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-social-bot-detection-265bf6f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hj_RSs1c6lq-TEIupyGm7

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 onvexia-social-bot-detection-265bf6f1
```

Example prompt: Check whether the social engagement around $PEPE is coming from real accounts or bots — I want to know if its hype is organic before I make a move.

## When to prefer this

Choose this endpoint when you need to assess the authenticity of social activity specifically in the context of blockchain assets — particularly when cross-referencing on-chain data with social signals is important. It is preferred over generic bot-detection APIs when the asset context (token, chain, address labels) matters for the analysis, or when you are already using Onvexia for broader blockchain analytics.

## Known failure modes

- Empty data array if no matching social records found for the given properties
- Malformed or missing `properties` parameter returns schema validation error
- Upstream analytics data may lag for very new or low-volume assets
- Rate limiting or payment failure returns 402 if USDC micropayment is not attached
- Unknown or unsupported asset identifiers may yield empty results

## How this service works

Thousands of assets across ten chains, half a million analysed documents, labelled addresses and supply-age history reaching back to 2008 — fused into one reading per asset. REST, SQL, GraphQL and MCP.

## Output

Returns a JSON object with a `data` array containing bot detection assessments for the queried social entities, and a `meta` object with endpoint and documentation references. Each data entry likely includes authenticity signals, bot likelihood scores, and flagged account properties derived from Onvexia's cross-chain social analytics corpus.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "meta": {
   "docs": "https://onvexia.com/openapi.json",
   "endpoint": "/v1/social/bot-detection"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-social-bot-detection-265bf6f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onvexia.com](https://www.zero.xyz/host/onvexia.com/llms.txt)