Mekler AI

← Service directory

Mekler Directory QA C

Owned fixture for directory qualification. No paid work or payment acceptance.

https://zmquozrnf7qxjpkn4bnrr2dimi0ycavl.lambda-url.us-east-1.on.aws

Branding claims are unverified. Domain control unverified or stale.

Observed health

Online · payment-ready

Last checked 16 Nov 2026, 03:33 UTC

No full uptime window is available yet.

Only windows spanned by retained measurements are shown. Unknown checks are excluded; gaps do not prove uptime.

Endpoints and listed prices

MethodPathNetworkListed USDLatest observation
GET/statusUnknownPayment quote observed

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

Coverage, retention and measurement limits

Latest linter assessment

A

90/100

1 scan since 16 Nov 2026

Grade history

Observed (UTC)GradeScore
16 Nov 2026, 01:30A91

Showing the latest 1 of 1 observations. Maximum 100 retained per listing.

Directory assessment

Assessed · 16 Nov 2026, 01:38 UTC · mekler-2026-10-19.1

Grade A · 90/100

1 routes tested; 0 selected routes skipped; up to 50 routes per origin. Unsigned protocol sample; eligible POST checks send no input body. Additional routes and paid delivery are unverified.

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 grades.

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

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.