api.ukintel.uk
https://api.ukintel.uk/v1/company/:number/verdictShares a payout wallet with 7 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Check any UK company is real, active and safe to deal with. One call returns Companies House registration, filing health, officer stability and an FCA-regulation cross-check as clean JSON with a 0-100 risk verdict, named flags you can audit, and a two-sentence plain-English narrative. Scores are computed by deterministic rules, never by a language model.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
0.0% avgResponse time
Data table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/15/2026, 2:00:00 AM | 0% | 1 | — |
| 8/16/2026, 2:00:00 AM | 0% | 1 | — |
| 8/17/2026, 2:00:00 AM | 0% | 1 | — |
| 8/18/2026, 2:00:00 AM | 0% | 1 | — |
| 8/19/2026, 2:00:00 AM | 0% | 1 | — |
| 8/20/2026, 2:00:00 AM | 0% | 1 | — |
| 8/21/2026, 2:00:00 AM | 0% | 1 | — |
- Availability
- 0
- Latency
- not yet measured
- Security
- 100
- Transparency
- 30
- Activity
- 6
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 22% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- —
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 8/20/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/10/2026 | 1 | 0.1 | 1 |
| 8/12/2026 | 1 | 0.15 | 1 |
| 8/17/2026 | 2 | 0.01 | 2 |
| 8/18/2026 | 13 | 1.22 | 1 |
| 8/20/2026 | 1 | 0.02 | 1 |
Payout address changed 1 time, last on 8/18/2026
- 0x1Da3…7C1d → 0x8aa6…aab4 (base) · 8/18/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 8 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.