Mekler AI

← Service directory

IBAN & Tax Verification Hub

13 endpoints (2 GET, 11 POST), including GET /api/curs-bnr, POST /api/valideaza-cui and POST /api/audit-partener.

Not yet claimed

Payment check

✓ Passed

Health

Loading health…

Health data

Integration score

91

Score checked

Price not available

View endpoints

Is this your service?

Claim it free
Endpoints

Endpoint details

MethodPathNetworkListed USDLatest observation
POST/api/converteste-valutaBase$0.004Reading unavailable
POST/api/valideaza-cuiBase$0.01Reading unavailable
POST/api/valideaza-ibanBase$0.002Reading unavailable
POST/api/audit-partenerBase$0.025Reading unavailable
POST/api/sign-transactionBase$0.004Reading unavailable
GET/api/generate-uuidv7Base$0.002Reading unavailable
POST/api/generate-efactura-ublBase$0.03Reading unavailable
GET/api/curs-bnrBase$0.004Reading unavailable
POST/api/valideaza-iban/batchBase$0.025Reading unavailable
POST/api/verify-signatureBase$0.003Reading unavailable
POST/api/iban/generate-epc-qrBase$0.002Reading unavailable
POST/api/hash-timestampBase$0.003Reading unavailable
POST/api/generate-idempotency-keyBase$0.002Reading unavailable

Read endpoint observations in the listing API

Listed prices are source claims; the provider’s current payment quote controls. An unsigned payment challenge does not prove useful paid delivery.

Data: x402-list.com (CC BY 4.0)

Coverage, retention and measurement limits

Bazaar-reported activity

10 calls across 2 exact matched resources in the source’s trailing 30-day windows. Counts may include self-funded activity and are not independently verified finalized settlements.

Observed 05 Nov 2026, 00:47 UTC. Missing resources remain unknown.

Check details

Why this score

Each area starts at 100. Failed or warning checks subtract fixed penalties within that area; it cannot fall below zero. Area scores are weighted 50% protocol, 35% documentation and 15% discovery, then the total is rounded. Unknown and skipped checks do not subtract points.

Directory assessment: Assessed · 2026-11-19 15:04 UTC · mekler-2026-10-19.1

At the dated assessment we tested all 24 selected routes. This table lists 13 routes active now; the assessment can include documentation routes not listed here.

This grade covers a bounded sample of unsigned protocol requests.

Eligible POST checks send no input body, credential or payment. Additional endpoints and useful paid delivery remain unverified.

Claiming or paying does not influence assessments.

Check results (39)

Protocol

  • P1 “Public endpoint is reachable”: pass
  • P2 “Paid route returns a payment challenge”: pass
  • P3 “Challenge follows the x402 schema”: pass
  • P4 “Payment challenge header is present”: pass
  • P5 “HEAD returns no settlement receipt”: pass
  • P6 “Price uses positive atomic units”: pass
  • P7 “Payout is consistent per network and token”: pass
  • P8 “Description fits the protocol limit”: pass

Documentation

  • S1 “OpenAPI document is available”: pass
  • S2 “x402 security scheme is declared”: fail. Declare PAYMENT-SIGNATURE as an x402 header security scheme.
  • S3 “Free operations declare no authentication”: skip
  • S4 “Paid operations document payment”: fail. Declare x402 security and a 402 response for paid operations.
  • S5 “POST challenge includes discovery metadata”: pass
  • S6 “Service manifest is available”: pass
  • S7 “Agent instructions link to the API”: pass
  • S8 “Agent card is available”: fail. Publish a valid agent card at /.well-known/agent-card.json.
  • S9 “Homepage links to discovery documents”: fail. Link API documentation from the origin root.
  • S10 “Robots policy permits discovery”: pass
  • S11 “Local schema references resolve”: pass
  • S12 “Service icon is available”: pass

Discovery

  • D1 “Directory registration”: unknown
  • D2 “Directory resource freshness”: unknown
  • D3 “Recent settlement evidence”: unknown
  • D4 “On-chain adoption evidence”: unknown
  • D5 “x402 ecosystem registration”: unknown

Additional payment diagnostics

Separate compliance diagnostics do not contribute to the integration score.

  • C1 “Capture an HTTP 402 challenge”: pass
  • C2 “Provide payment alternatives array”: pass
  • C3 “Provide payout addresses”: pass
  • C4 “Include payout in first alternative”: pass
  • C5 “Use valid chain address syntax”: pass
  • C6 “Specify atomic-unit price”: pass
  • C7 “Use positive bounded atomic price”: pass
  • C8 “Supply token address”: pass
  • C9 “Use a CAIP-2 network”: pass
  • C10 “Specify exact payment scheme”: pass
  • C11 “Use HTTPS”: pass
  • C12 “Declare protocol version 2”: pass
  • C13 “Supply EVM signing domain name and version”: pass
  • C14 “Provide PAYMENT-REQUIRED header”: pass
Past checks

This profile shows the Directory assessment observed 2026-11-19 15:04 UTC. Directory assessments and linter scans are separate automated checks.

Observed (UTC)Integration scorePayment checkSource
2026-11-19 15:04 UTC91✓ PassedDirectory assessment · shown
2026-11-15 16:59 UTC—Not assessed

Our checker could not read this service's robots.txt, so no grade was made.

Directory assessment

Showing 2 of 2 retained observations (consecutive attempts without a grade are grouped).

Earlier Directory assessments were not retained.

How checks work · Correct this listing