# Losbeto Ecosystem Pulse — Agent-Traffic Intelligence

> Losbeto Ecosystem Pulse — Agent-Traffic Intelligence is a paid API for AI agents from api.losbeto.xyz, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-12).

Returns first-party agent-traffic intelligence from Losbeto's own request stream: most-probed endpoints with heat scores, 7-day vs prior-7-day demand trends (Poisson z-score), unique agent-IP counts, QoS monitor share, and emerging demand clusters from weekly embedding clustering.

## Facts

- Endpoint: GET https://api.losbeto.xyz/ecosystem-pulse?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/losbeto-ecosystem-pulse-agent-traffic-intelligence-9e521a23
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Uy99ozTXTvgeJ7uuhhPGn

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 losbeto-ecosystem-pulse-agent-traffic-intelligence-9e521a23
```

Example prompt: Pull the latest ecosystem pulse from Losbeto — I want to see which x402 endpoints are hottest right now, the 7-day demand trend scores, and any emerging demand clusters forming in the agent swarm.

## When to prefer this

Choose this endpoint when you need first-party, node-level agent-traffic intelligence specific to the Losbeto swarm rather than general web analytics. It is uniquely suited for x402 builders sizing demand before launching a new pay-per-call service, for agents monitoring which endpoints are trending up or down in the agentic ecosystem, and for discovering emerging demand clusters before they become obvious. Prefer this over generic API analytics or third-party traffic estimators when you want Poisson-scored trend signals and embedding-derived cluster intelligence derived directly from real agent probe traffic.

## Known failure modes

- No query parameters required so malformed input is unlikely; stale data if the node's request stream has a gap
- Payment failure via x402 if USDC balance is insufficient (402 response)
- Rate limiting if the caller exceeds per-IP probe quotas
- Sparse cluster output if fewer than a week of embedding data has been collected
- Empty or null trend deltas if the endpoint was newly added within the prior 7-day window

## How this service works

First-party agent-traffic intelligence from this node's own request stream (~64k probes/day): most-probed endpoints with a heat score, 7d-vs-previous-7d demand trends (Poisson z-score), unique agent-IP counts, QoS-mon...

## Output

Returns a structured snapshot of agent-traffic analytics from Losbeto's own ~64k-probes/day request stream, including: a ranked list of most-probed endpoints with heat scores, 7-day vs prior-7-day demand trend deltas expressed as Poisson z-scores, unique agent-IP counts per endpoint, QoS monitor participation share, and emerging demand clusters identified via weekly on-node embedding clustering.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/losbeto-ecosystem-pulse-agent-traffic-intelligence-9e521a23/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.losbeto.xyz](https://www.zero.xyz/host/api.losbeto.xyz/llms.txt)