Leaderboard / api.aiskills402.com / endpoint
GET https://api.aiskills402.com/v1/skills/iam-policy-review/file
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
- Web audit by llm, confidence 35%
- Latest quote
- $0.01 on Base to 0xbc0d…2e68
- Uptime
- 100% / 7d, 100% / 30d
- Delivery
- none not yet paid-tested
- HTTPS
- yes
- First listed
- 2026-11-16
- Last probe
- 3h ago
- Next probe
- 2026-11-17 23:30 UTC
Score components
Catalog listings
| Source | Scheme | Network | Asset | Listed price | Pay to | Flow | Current | Last seen |
|---|---|---|---|---|---|---|---|---|
| cdp | exact | Base | 0x8335…2913 | $0.01 | 0xbc0d…2e68 | default | yes | 39m 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 |
|---|---|---|---|---|---|
| 13h ago | Web audit | 35% | llm | v1 | claude-haiku-5-5: The endpoint reviews a supplied AWS IAM policy JSON for overly broad grants and returns findings with fixes. It is a security audit of a user-supplied artifact, closest to web_audit (audits of a target the caller supplies), though it is not a web site audit, so confidence is moderate-low. Compliance is another possible fit but the focus is least-privilege security review. |
| 22h ago | Other | 40% | rules | v1 | rule none matched "" in none |
Probe history
| When | Kind | Status | Latency | x402 | Valid | Quoted | Pay to | Flags |
|---|---|---|---|---|---|---|---|---|
| 3h ago | free | 402 | 197 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 9h ago | free | 402 | 209 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 15h ago | free | 402 | 208 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 21h ago | free | 402 | 844 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 28h ago | free | 402 | 221 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 34h ago | free | 402 | 183 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |
| 40h ago | free | 402 | 206 ms | v2 | yes | $0.01 | 0xbc0d…2e68 | — |