Mekler AI

← Service directory

Chainlink for Agents

Explore source-listed blockchain and financial-data endpoints.

https://agents.chain.link

Branding claims are unverified. Domain control unverified or stale.

Observed health

Degraded · payment-ready

Last checked 14 Nov 2026, 16:33 UTC

Uptime across rolling day windows: 1d: 100.0%, 30d: 99.93%, 7d: 100.0%, 90d: 99.93%

Endpoints and listed prices

MethodPathNetworkListed USDLatest observation
POST/v1/registereip155:84530.002Payment quote observed
POST/v1/operations/:operationId/submiteip155:84530.002Requires request parameters

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

2 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 11 Nov 2026, 00:55 UTC. Missing resources remain unknown.

Directory assessment

Unassessed · 14 Nov 2026, 04:55 UTC · mekler-2026-10-19.1

No grade from the available evidence.

0 routes tested; 0 selected routes skipped; up to 50 routes per origin. Read-only sample; additional routes and paid delivery are unverified.

No safe routes observed. Claiming or paying does not influence grades.

Check results (39)
  • P1: unknown
  • P2: unknown
  • P3: unknown
  • P4: unknown
  • P5: unknown
  • P6: unknown
  • P7: unknown
  • P8: unknown
  • S1: fail. Publish a valid OpenAPI document at /openapi.json.
  • S2: fail. Declare PAYMENT-SIGNATURE as an x402 header security scheme.
  • S3: skip
  • S4: unknown
  • S5: skip
  • S6: fail. Publish a machine-readable /.well-known/x402 manifest.
  • S7: fail. Publish a useful /llms.txt with API links.
  • S8: fail. Publish a valid agent card at /.well-known/agent-card.json.
  • S9: fail. Link API documentation from the origin root.
  • S10: pass
  • S11: unknown
  • S12: fail. Serve a favicon.
  • D1: unknown
  • D2: unknown
  • D3: unknown
  • D4: unknown
  • D5: unknown
  • C1: fail. See the published check rules.
  • C2: fail. See the published check rules.
  • C3: fail. See the published check rules.
  • C4: fail. See the published check rules.
  • C5: unknown
  • C6: unknown
  • C7: unknown
  • C8: unknown
  • C9: unknown
  • C10: unknown
  • C11: unknown
  • C12: unknown
  • C13: skip
  • C14: unknown

Claim or correct this listing →

Control this listing

Start a domain ownership proof through the API or MCP. Generate a private random requester key, publish the returned challenge JSON at your HTTPS well-known URL, then confirm with the same key. Confirmation returns a private 90 day credential. Use it with the current revision to hide your listing or suppress branding. Proof is rechecked after seven days; you can revoke access at any time.

Ownership does not change a technical grade or approve branding. Never put the control credential in the public challenge file.

Read the complete ownership and preferences contract

Configuration observations are not safety, semantic quality or paid-delivery certification.