# Losbeto Geo Alpha

> Losbeto Geo Alpha is a paid API for AI agents from losbeto-production-dd7c.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns geolocation-enriched data via a monetized x402 endpoint, payable with USDC micropayments on Solana or Base.

## Facts

- Endpoint: GET https://losbeto-production-dd7c.up.railway.app/geo-alpha
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/losbeto-geo-alpha-ef48aea1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1mwGM97bFF8QGS6MgiTMv

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-geo-alpha-ef48aea1
```

Example prompt: Can you pull the geo alpha data for this location using the Losbeto endpoint — I'll pay the $0.01 USDC per call via x402 on Solana?

## When to prefer this

Choose this endpoint when you need lightweight geolocation or geographic enrichment data and want to pay per-call via USDC micropayments using the x402 protocol on Solana or Base. It is well-suited for AI agent workflows that require metered, on-chain-accountable data access without subscription overhead.

## Known failure modes

- Payment not received — returns HTTP 402 requiring x402 USDC payment on Solana or Base
- Invalid or missing 'properties' parameter — may return empty or malformed JSON
- Endpoint downtime on Railway deployment — connection timeout or 5xx error
- Insufficient USDC balance — payment facilitation fails before data is returned
- Ambiguous input properties — returns generic or null geographic data

## How this service works

Losbeto: 67 endpoints x402 monetizados. Solana + Base. USDC micropayments para AI agents. Preços a partir de $0.003.

## Output

A JSON object containing geolocation and geographic metadata fields corresponding to the queried properties parameter. The exact schema is minimal but expected to include location identifiers, region data, or alpha signals relevant to the geo query.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/losbeto-geo-alpha-ef48aea1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from losbeto-production-dd7c.up.railway.app](https://www.zero.xyz/host/losbeto-production-dd7c.up.railway.app/llms.txt)