Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

api.munition.io

Paid API · api.munition.io · found in a public registry · checked since 2026-10-16

Client error (4xx) · latest check

As JSON

POST https://api.munition.io/v1/firecrawl/scrape$0.015 per call · from the registry's payment terms

The name is the registry's label, not ours. Not reviewed by a person. See 16 endpoints from munition.io.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

0 passed, 2 failed, 28 not run.

Passed, 30 daysshort history0 of 2 run
Checks missed0in 30 days
Response, latest243 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-161 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Details

Payment terms

Price per call
$0.015
Protocols
none seen yet
Networks
eip155:8453eip155:137eip155:42161solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Terms changes, 90 days
no valid payment request yet

Price from the registry's payment terms; protocols and networks as the registry states. Definitions

Reported by the registry

Payers, 30 days
6
Paid calls, 30 days
15

The registry's own figures, not our measurements.

Listing

In the capability tree: Web access and automation / Fetch and extract pages (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-18. Wrong place? Tell us.

In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✗ its latest check did not pass; ✓ at least 5 payers in 30 days (registry figure).

Purpose tags: none in the registry

Recent probes

WhenResultNetworks offeredTime to headers

cloudflare:MIA		 Client error (4xx) HTTP 400
expected 402 payment challenge		 — 243 ms

cloudflare:LHR		 Client error (4xx) HTTP 400
expected 402 payment challenge		 — 279 ms

What these figures do not show

  • A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
  • Payer and call counts are the registry's own figures, not our measurements.
  • The registry's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_d7fc4c6076287192