Leaderboard / palmyr.ai / endpoint
POST https://palmyr.ai/phone/numbers/:id/wait-otp
Scores measure reliability and honesty, not output quality.
- Listed only 2 days ago; new listings earn trust over 30 days.
- Answered all 11 probes in the last 7 days.
- Category
- Email by llm, confidence 60%
- Latest quote
- $0.02 on Base to 0x79e9…3881
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- Observed
- none reported yet (opt-in wrapper telemetry)
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 50m ago
- Next probe
- 2026-11-19 01:24 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.02 | 0x79e9…3881 | default | yes | 3h ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 20000 | GqSs5L…SgkM | default | yes | 3h ago |
Paid probes
No paid probes yet. Paid probing is off by default and runs weekly per host under a strict spend cap; each paid probe links to its on-chain transaction here.
Delivery checks
Inside each paid probe we ask for something whose correct answer we know, then compare. A pass means the seller delivered what it was paid for; a fail means it charged and returned something wrong; inconclusive means we could not judge (no reference, unknown input shape, or a non-2xx response). Every row carries the request, the response hash and the reference so the verdict can be reproduced. Judged results feed the "Delivery after payment" component (pass 1, error after payment 0.25, fail 0); inconclusive rows are excluded; a fail in the last 14 days caps the verdict at caution. Methodology.
No delivery checks yet. They run inside the weekly paid probe.
Classification history
Every classification is kept; the newest row is the current category. Rules match the listing text; the model is consulted only when the rules are unsure.
| When | Category | Confidence | Method | Version | Evidence |
|---|---|---|---|---|---|
| 43h ago | 60% | llm | v1 | claude-haiku-5-5: The endpoint waits for and returns an SMS one-time code sent to a phone number, which is a messaging receive function. Email is the closest listed category for receiving and parsing inbound messages; no SMS or telecom category exists, so confidence is moderate. Phone number is the main ambiguity. | |
| 47h ago | Data transform | 60% | rules | v1 | rule data_transform matched "regex" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 50m ago | free | 402 | 1234 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 8h ago | free | 402 | 627 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 14h ago | free | 402 | 677 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 20h ago | free | 402 | 650 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 27h ago | free | 402 | 651 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 33h ago | free | 402 | 644 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 40h ago | free | 402 | 564 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 46h ago | free | 402 | 701 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 2d ago | free | 402 | 325 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 2d ago | free | 402 | 251 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |
| 3d ago | free | 402 | 237 ms | v2 | yes | $0.02 | 0x79e9…3881 | — |