Mekler AI

← Service directory

Fieldwright API by CyberMax

1 GET endpoint: /x402/api/extract. Observed price $0.004 on Base.

https://fieldwright.cybermaxtools.com

Branding claims are unverified. Domain control unverified or stale.

Payment check

✓ Passed

All 3 required checks passed.

3 of 3 required checks passed · observed 2026-11-18 01:23 UTC. No payment or useful paid delivery was tested.

Health now

Health is checked every 15 minutes; current status loads below.

Directory health · Current health in the listing API

Integration score

90

A weighted penalty score for protocol, documentation and discovery checks. This is not the percentage of checks passed.

Protocol100 / 10050% weight
Documentation70 / 10035% weight
Discovery100 / 10015% weight

Observed 2026-11-18 01:23 UTC. Unknown and skipped checks do not subtract points. How this score is calculated

Endpoints and listed prices

MethodPathNetworkListed USDLatest observation
GET/x402/api/extracteip155:84530.004See 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

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-18 01:23 UTC · mekler-2026-10-19.1

At the dated assessment we tested 1 of 2 selected routes and skipped 1 under the free-check policy (for example, POST routes that need input). This table lists 1 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”: fail. Explicitly set security to [] for free operations.
  • S4 “Paid operations document payment”: fail. Declare x402 security and a 402 response for paid operations.
  • S5 “POST challenge includes discovery metadata”: skip
  • S6 “Service manifest is available”: pass
  • S7 “Agent instructions link to the API”: pass
  • S8 “Agent card is available”: pass
  • S9 “Homepage links to discovery documents”: pass
  • 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

Assessment history

This profile shows the Directory assessment observed 2026-11-18 01:23 UTC. Directory assessments and linter scans are separate automated checks.

Observed (UTC)Integration scorePayment checkSourceRules version
2026-11-18 01:23 UTC90✓ PassedDirectory assessment · shownmekler-2026-10-19.1
2026-11-16 13:57 UTC—Not assessed

The available checks could not produce a grade because of input, authentication, rate limits or network conditions.

Directory assessmentmekler-2026-10-19.1

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

Earlier Directory assessments were not retained.

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.