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

gpt55.558686.xyz

Paid API · gpt55.558686.xyz · found in a public registry · checked since 2026-10-17

Redirect not followed · latest check

As JSON

GET https://gpt55.558686.xyz/v1/tools/wallet-signing-safety-pack$0.018 per call · from the registry's payment terms

The name is the registry's label, not ours. Not reviewed by a person. See 153 endpoints from 558686.xyz.

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, latest1060 msto first headers
Scheduledailyset by usage; rule below
Checked since2026-10-172 days
Freshnessfreshagainst its schedule

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

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours00——————
7 dayssince 2026-10-1700——————
30 dayssince 2026-10-1700——————

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.018
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

Access

Our latest check
not observed
Stated
not stated
Payment model
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-10-17. Wrong place? Tell us.

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

Purpose tags: none in the registry

Recent probes

WhenResultNetworks offeredTime to headers

cloudflare:MIA
Redirect not followed HTTP 308
expected 402 payment challenge
— 1060 ms

cloudflare:EWR
Redirect not followed HTTP 308
expected 402 payment challenge
— 594 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 2 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_1500e3cdbb4b5019