Live endpoints
Request an API key
One HTTPS call in. A scored, explained verdict out: action, reasons, evidence and confidence. EU-built, PII-free, fail-closed auth, pay per call.
No raw PII, ever. Send opaque signal ids and context. Get back an action, a score and the reason behind it, in one round trip.
"degraded": true.# POST a signal bundle, get one explained decision back curl -X POST https://vilkax.com/api/partner/v1/decide \ -H "Authorization: Bearer $VILKAX_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "signals": [ { "id": "process.remote_access_tool", "value": 0.9 }, { "id": "text.urgency_pressure", "value": 0.8 }, { "id": "transfer.outbound_initiated", "value": 1.0 } ], "context": { "action_kind": "transfer" } }' → { "action": "review", "score": 84, "why": "Remote-access tool + urgency during a transfer." }
Get a key, make one call, act on the verdict. Every example targets a real, live endpoint.
vlx_live_… and a tier. The plaintext is shown once; we store only its SHA-256 hash.Authorization: Bearer on every request. Each endpoint needs a scope the key carries.usage is free.Real, deployed routes on https://vilkax.com. Fields add, never break.
signals:* grant the family. Under-scoped keys fail closed."degraded": true. Never a false all-clear.One call returns a 0 to 100 hazard score and an advisory verdict. If an order disputes, the representment evidence packet is ready to file with your acquirer.
Lookups bill 1 unit, deep calls 3, usage is free. No seat fees.
Request one from the contact form. We issue your vlx_live_ key and tier; the plaintext is shown exactly once. A self-serve portal is on the way.
No. Decisioning endpoints take opaque signal ids only; raw PII is rejected with pii_in_features. Lookup values (email, phone, domain, IP, wallet) are hashed server-side.
Yes, via the guard:* scope family. POST to /api/business/v1/guard/evaluate with a hashed order (no raw PII) and get back a 0 to 100 hazard score and an advisory verdict. If that order later disputes, POST the chargeback to /guard/dispute and receive a representment evidence packet, reason-code classification, evidence mapping and dispute strategy, ready to file with your acquirer.
They score isolated purchase signals within their merchant network. Guard additionally draws from the Vilkax anti-scam intelligence layer, the consumer-side behaviour patterns and entity-graph signals that protect people. An inbound counterparty can be scored against known social-engineering victim and mule patterns before the transaction posts. The advisory score is native to the API call, not a separate integration.
Start free, wire one call, and decide with evidence from day one. We issue your vlx_live_ key and tier.
Not building yet? Get on the developer early-access list and we'll email you the moment the Protect API opens.