VERIDEX

Reviewed 1d ago.

• tools: 3 tools scanned
• metadata: scanned

No findings.

Tools (3)

• verify_company_by_cif

  Verify a Spanish company by its CIF and get its registry data, status in the BORME, recent published acts and an explainable 0-100 risk score. This is an x402-paid endpoint. The first call returns ok=false with error.code='payment_required' and a complete `payment` challenge (price, network, asset, receiving address). Settle that challenge with a wallet you control and call again with the resulting base64 payload in `x_payment`; the same call then returns the company. Errors are typed: 'not_found' (valid CIF, no record — you are not charged), 'source_unavailable' (upstream registry down — not charged, safe to retry), 'invalid_request' (malformed CIF), 'rate_limited' (quota), 'transport_error' (the API was unreachable). Do not retry a 402 without changing the payment.

• get_veridex_info

  Describe the VERIDEX service: what it does, its price, the settlement network and asset, the receiving address and the available endpoints. Reads the public discovery manifest at /.well-known/x402. Needs no credentials and costs nothing. Call this before verifying if you need to know what a verification costs or where the payment goes.

• health_check

  Check whether the VERIDEX API is up, and see today's demand: uptime, the number of verification calls served today and the distinct callers. Free and unauthenticated. The request count excludes the service's own healthchecks and local tests, so it answers 'is anyone using this?' rather than 'is the process alive?'. Useful before starting a paid flow.