Leaderboard / agent402.tools / endpoint
POST https://agent402.tools/api/skill/user-onboarding
Scores measure reliability and honesty, not output quality.
- Listed only 1 day ago; new listings earn trust over 30 days.
- Answered all 7 probes in the last 7 days.
- Category
- Data transform by llm, confidence 50%
- Latest quote
- $0.008 on Base to 0xaBF4…a9D0
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 2h ago
- Next probe
- 2026-11-17 23:48 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Polygon | 0x3c49…3359 | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | eip155:4663 | 0x5fc5…d168 | 10000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | eip155:42220 | 0xcebA…118C | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | Base | 0x8335…2913 | $0.008 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | eip155:57073 | 0x2D27…EAEd | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | upto | Base | 0x8335…2913 | $0.008 | 0xaBF4…a9D0 | permit2 | yes | 22m ago |
| cdp | exact | algorand:wGHE2Pwdvd7S12BL5FaOP20EGYesN73k | 31566704 | 8000 | C7IIHG…2XIE | default | yes | 22m ago |
| cdp | exact | eip155:1329 | 0xe15f…2392 | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | Arbitrum | 0xaf88…5831 | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | eip155:143 | 0x7547…b603 | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | Avalanche | 0xB97E…8a6E | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | eip155:10 | 0x0b2C…Ff85 | 9000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| cdp | exact | Solana | EPjFWd…Dt1v | 8000 | J7aN3P…3xwg | default | yes | 22m ago |
| cdp | exact | stellar:pubnet | CCW67T…MI75 | 80000 | GDNJXC…WWRL | default | yes | 22m ago |
| cdp | exact | eip155:5042 | 0x3600…0000 | 8000 | 0xaBF4…a9D0 | default | yes | 22m ago |
| payai | exact | Solana | EPjFWd…Dt1v | 8000 | J7aN3P…3xwg | default | yes | 7m ago |
| payai | exact | Base | 0x8335…2913 | $0.008 | 0xaBF4…a9D0 | default | yes | 7m ago |
Listing changes
| When | Event | From | To |
|---|---|---|---|
| 10m ago | disappeared | — | — |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | price_changed | 8000 | 10000 |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
| 22m ago | description_changed | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call. | Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup. |
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 |
|---|---|---|---|---|---|
| 43s ago | Data transform | 50% | llm | v1 | claude-haiku-5-5: The endpoint runs a deterministic onboarding workflow (hashing, handle derivation, ID minting, TOTP verification) and returns processed signup data, which fits deterministic transforms best. It also touches email validation, which could suggest email, but the core output is transformed records rather than email sending or validation as a service. |
| 2m ago | 60% | rules | v1 | rule email matched "validate the email" in description | |
| 6h ago | Data transform | 60% | llm | v1 | claude-haiku-5-5: The endpoint runs a deterministic, pure-CPU onboarding pipeline: email validation, password scoring, hashing, handle derivation and TOTP verification. The closest match is deterministic transforms such as hashes and encodings, though it also touches email validation and 2FA, so confidence is moderate. |
| 22h ago | 60% | rules | v1 | rule email matched "validate the email" in description |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 2h ago | free | 402 | 427 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 9h ago | free | 402 | 690 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 15h ago | free | 402 | 112 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 21h ago | free | 402 | 81 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 27h ago | free | 402 | 308 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 33h ago | free | 402 | 68 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |
| 39h ago | free | 402 | 78 ms | v2 | yes | $0.008 | 0xaBF4…a9D0 | — |