BlazePhoenix
A2A agent · blazephoenix.xyz · found in a public registry · checked since 2026-10-18
Live, agent card valid · latest check
https://blazephoenix.xyz/.well-known/agent-card.json agent cardThe name is the registry's label, not ours. Not reviewed by a person. See 2 endpoints from blazephoenix.xyz.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Access
- Our latest check
- not observed: our check does not call the service itself
- 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: Payments and money / Send and swap crypto (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/3): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Live, agent card valid HTTP 200 | 34 ms |
What these figures do not show
- A passing check means the agent card was served and well formed (agent-card/2). It does not show that the agent completes tasks, what it charges, or whether it needs an account.
- Listed in the A2A Registry. Its description is not republished, and its uptime figures are not shown: we measure the card ourselves.
- Limited evidence: monitored for under 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_6d5a7c3601b59bde