Beggar Bot /v1/cronparse

1 route settlement-verified · $0.02 USDC/request · 1 endpoint · Data · base network · x402 protocol

Verified routes

GET /v1/cronparse · $0.02 · Verified with a $0.02 test payment on 12 Nov 2026 · receipt

Other routes are unverified.

Networks: Base (settlement-verified)

Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.

url https://payapi.market/mcp

Listing facts

Provider: Beggar Bot
Hosted at: beggar-bot-demand.beggarbot.workers.dev
Category: Data
Price: $0.02 USDC per request
Payment networks: Base
Settlement-verified: 1 route, last checked 2026-11-12
Listed on PayAPI Market: 2026-11-01

Try Beggar Bot /v1/cronparse

Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.

curl -i "https://beggar-bot-demand.beggarbot.workers.dev/v1/cronparse"

About this API

Beggar Bot /v1/cronparse is listed in the Data category with pricing at $0.02 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-11-12. View receipt on Basescan.

Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.

This API exposes 1 endpoint.

Add this badge to your README

Paste this on your site. The link points at this listing. Listing is free and providers keep 100%.

Markdown

[![Settlement-verified on PayAPI Market](https://payapi.market/badge/beggar-bot-v1-cronparse.svg)](https://payapi.market/api/beggar-bot-v1-cronparse)

HTML

<a href="https://payapi.market/api/beggar-bot-v1-cronparse"><img src="https://payapi.market/badge/beggar-bot-v1-cronparse.svg" alt="Settlement-verified on PayAPI Market" height="20"></a>

What this badge means

Questions about this API

What does Beggar Bot /v1/cronparse do?

Beggar Bot /v1/cronparse It is provided by Beggar Bot.

How much does Beggar Bot /v1/cronparse cost?

Beggar Bot /v1/cronparse is priced at $0.02 USDC per request, paid per call with no subscription. Verified with a $0.02 test payment on 12 Nov 2026. The exact amount for each call is in the HTTP 402 response before any money moves.

Do I need an API key or account to use Beggar Bot /v1/cronparse?

No. Beggar Bot /v1/cronparse uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.

Has Beggar Bot /v1/cronparse been verified?

Yes, 1 route. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-11-12.

How does an AI agent find Beggar Bot /v1/cronparse?

Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.

More Data APIs · Browse the marketplace · List your own API

Related APIs

Call before classifying German health-insurance obligation · 1 route verified · Call before classifying German health-insurance obligation. Returns the 2026 Jahresarbeitsentgeltgrenzen. Not the pension ceiling.
Call before German payroll uses a contribution ceiling · 1 route verified · Call before German payroll uses a contribution ceiling. Returns the 2026 ceilings and Bezugsgröße. Not a contribution rate.
Call before a German VAT filing treats a trader as a small business · 1 route verified · Call before a German VAT filing treats a trader as a small business. Returns the published § 19 Abs. 1 thresholds for 2026. Not a ruling.
Call before payroll uses the German statutory minimum wage · 1 route verified · Call before payroll uses the German statutory minimum wage. Stored rates from § 1 MiLoV5 only. Not a sector wage.
Context trim · 1 route verified · Context trim. Any text in, URL-encoded as the text query parameter (up to 12,000 bytes), a leaner rendering out: line endings normalized, trailing whitespace stripped, blank runs collapsed, adjacent d
JSON to Markdown · 1 route verified · JSON to Markdown. Any JSON document in, URL-encoded as the json query parameter (up to 12,000 bytes), a clean Markdown rendering out: object keys as headed sections, uniform object arrays as tables, s

More from Beggar Bot

By Beggar Bot