AIOptiTech Prompt Library prompt
Paid API · api.aioptitech.com · found in a public list · checked since 2026-10-23
Client error (4xx) · latest check
GET https://api.aioptitech.com/v1/prompts/:id$0.05 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. The URL contains placeholders (such as :address) that callers fill in. We check it with a sample value of the right form in each placeholder (a documentation value such as example.com, a null value such as the zero address, or a common sample such as 1), and each check records the address we requested. If the service rejects that address (400, 404, 410 or 422), the check is recorded as "couldn't test as listed": neither a pass nor a failure, and left out of pass rates.
Our checks
An unpaid request daily, from eastern North AmericaLast 2 checks, oldest to newest; room for 28 more
0 passed, 2 failed, 28 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 0 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-23 | 0 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-23 | 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.05
- 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
- 1
- Paid calls, 30 days
- 1
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-10-23. 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
We check it with a sample value of the right form in each placeholder (a documentation value such as example.com, a null value such as the zero address, or a common sample such as 1), and each check records the address we requested. If the service rejects that address (400, 404, 410 or 422), the check is recorded as "couldn't test as listed": neither a pass nor a failure, and left out of pass rates.
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Client error (4xx) HTTP 404 expected 402 payment challenge |
— | 711 ms |
cloudflare:MIA |
Client error (4xx) HTTP 404 expected 402 payment challenge |
— | 322 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_3944ccab174109b7