Back to Browse
Strale VASP Non-Compliant Check
x402
Strale VASP Non-Compliant Check is a paid API for AI agents from api.strale.io, paid per call via x402, $0.0216/call, status unknown (last checked 2026-09-15).
Checks whether a company or entity is flagged as a non-compliant Virtual Asset Service Provider (VASP) across monitored watchlists or databases
Price / call$0.0216
Success—
StatusUnknown
How this service works
The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.
Output
Returns whether the named entity is identified as a non-compliant VASP, along with supporting details about the flag status and a cryptographically hashed audit record for traceability.
Example use cases
Pre-onboarding VASP due diligence
“Before we onboard this new partner, can you check if 'BitVault Pro' is listed as a non-compliant VASP? Their site is bitvaultpro.io.”
Counterparty risk screening
“I'm about to send funds through 'SwiftCrypto Ltd' — can you quickly verify whether they're flagged as a non-compliant virtual asset service provider?”
Regulatory compliance audit workflow
“As part of our compliance review, run a non-compliant VASP check on 'Nexus Digital Assets' at nexusdigitalassets.com and tell me if there are any red flags.”
Technical details
Endpoint
GEThttps://api.strale.io/x402/v2/vasp-non-compliant-checkWhen to prefer
Use this endpoint when you need to screen a crypto company or virtual asset service provider for regulatory non-compliance before onboarding, transacting, or partnering. It is purpose-built for VASP-specific compliance checks with cryptographic audit trails, making it suitable for regulated environments requiring provable due diligence records. Prefer this over generic company lookup endpoints when the specific concern is VASP regulatory standing.
Side effects
- Missing required entity_name parameter returns a validation error
- Unknown or unrecognized entity may return no match rather than a definitive clear status
- Website parameter mismatch with entity name may produce ambiguous results
- Rate limiting or payment failure (x402) prevents the call from completing
- Entity name variations or aliases may cause missed matches
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"