market.datapackvibe.com
Paid API · market.datapackvibe.com · found in a public list · checked since 2026-10-17
Client error (4xx) · latest check
GET https://market.datapackvibe.com/x402/assistant-ib26-analytics-04-208$0.01 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 72187 endpoints from datapackvibe.com.
Our checks
An unpaid request monthly, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
0 passed, 1 failed, 29 not run.
Checked monthly. Usually daily: Daily: 5 to 99 payers, and every new service until it has been probed 3 times. Checked monthly instead because its host has more services than our per-host limit lets us check at their usual intervals. One host: we send at most 2 checks to one host every five minutes (576 a day). When a host's services at the intervals above would need more than 288 checks a day (half of that, leaving room to catch up), every service on that host is checked one interval slower (hourly becomes daily, daily weekly, weekly monthly), and again if needed, until they fit. Each such service says so.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 0 | 0 | — | — | — | — | — | — |
| 7 days | 0 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-17 | 0 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing nothing yet: no check of the current method has passed. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.01
- Protocols
- none seen yet
- Networks
- eip155:8453
- 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
- 2
- Paid calls, 30 days
- 5
The registry's own figures, not our measurements.
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-11-03. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✗ its latest check did not pass.
Purpose tags: none in the registry
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Client error (4xx) HTTP 405 expected 402 payment challenge |
— | 272 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 17 days (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_2c156af5c5c22483