Lumière PayCheck Free API key
Agent buildersAll endpointsFacilitatorsDocsPlansLumière Agents NewStatusSign inGet a free API key

Payments on Base + Solana

Payments on Base + Solana

Home › Sellers › www.mahastrategies.com

www.mahastrategies.com x402 API: grades and paid tests

www.mahastrategies.com has 1,156 x402 endpoints in our catalog. Right now: 61 proceed, 1,094 caution, 1 too new. 61 passed a real paid test: we paid the listed price and got what the listing promised. Best grade: A.

Every endpoint on www.mahastrategies.com

Best grades first. Open an endpoint for its full history: uptime, price and payout-wallet changes, and paid-test results with signed receipts.

EndpointGradeVerdictUptime (7 days)Response timePaid test passed
/api/v1/compute/robotics-telemetry/duplicate-record-identitiesC Caution100% 244 ms–
/api/v1/compute/robotics-telemetry/export-semantic-parityC Caution100% 228 ms–
/api/v1/compute/robotics-telemetry/identifier-crosswalk-auditC Caution100% 234 ms–
/api/v1/compute/robotics-telemetry/missingness-cooccurrenceC Caution100% 229 ms–
/api/v1/compute/robotics-telemetry/provenance-edge-auditC Caution100% 231 ms–
/api/v1/compute/robotics-telemetry/record-sequence-diffC Caution100% 223 ms–
/api/v1/compute/robotics-telemetry/reference-integrity-mapC Caution100% 224 ms–
/api/v1/compute/robotics-telemetry/required-field-coverageC Caution100% 234 ms–
/api/v1/compute/robotics-telemetry/revision-delta-mapC Caution100% 236 ms–
/api/v1/compute/robotics-telemetry/schema-directionalityC Caution100% 229 ms–
/api/v1/compute/robotics-telemetry/scope-boundary-auditC Caution100% 227 ms–
/api/v1/compute/robotics-telemetry/source-coverage-mapC Caution100% 244 ms–
/api/v1/compute/robotics-telemetry/timestamp-order-auditC Caution100% 241 ms–
/api/v1/compute/robotics-telemetry/unit-label-consistencyC Caution100% 228 ms–
/api/v1/compute/robotics/grid-dry-runC Caution100% 243 ms–
/api/v1/compute/signals/aliasing-checkC Caution100% 231 ms–
/api/v1/compute/spectrometry-records/condition-coverage-mapC Caution100% 280 ms–
/api/v1/compute/spectrometry-records/declared-bound-auditC Caution100% 265 ms–
/api/v1/compute/spectrometry-records/duplicate-record-identitiesC Caution100% 267 ms–
/api/v1/compute/spectrometry-records/export-semantic-parityC Caution100% 237 ms–
/api/v1/compute/spectrometry-records/identifier-crosswalk-auditC Caution100% 272 ms–
/api/v1/compute/spectrometry-records/missingness-cooccurrenceC Caution100% 240 ms–
/api/v1/compute/spectrometry-records/provenance-edge-auditC Caution100% 267 ms–
/api/v1/compute/spectrometry-records/record-sequence-diffC Caution100% 283 ms–
/api/v1/compute/spectrometry-records/reference-integrity-mapC Caution100% 241 ms–
/api/v1/compute/spectrometry-records/required-field-coverageC Caution100% 252 ms–
/api/v1/compute/spectrometry-records/revision-delta-mapC Caution100% 310 ms–
/api/v1/compute/spectrometry-records/schema-directionalityC Caution100% 238 ms–
/api/v1/compute/spectrometry-records/scope-boundary-auditC Caution100% 308 ms–
/api/v1/compute/spectrometry-records/source-coverage-mapC Caution100% 276 ms–
/api/v1/compute/spectrometry-records/timestamp-order-auditC Caution100% 221 ms–
/api/v1/compute/spectrometry-records/unit-label-consistencyC Caution100% 362 ms–
/api/v1/compute/terrain/profile-arithmeticC Caution100% 262 ms–
/api/v1/compute/thermal-measurements/condition-coverage-mapC Caution100% 258 ms–
/api/v1/compute/thermal-measurements/declared-bound-auditC Caution100% 272 ms–
/api/v1/compute/thermal-measurements/duplicate-record-identitiesC Caution100% 304 ms–
/api/v1/compute/thermal-measurements/export-semantic-parityC Caution100% 330 ms–
/api/v1/compute/thermal-measurements/identifier-crosswalk-auditC Caution100% 339 ms–
/api/v1/compute/thermal-measurements/missingness-cooccurrenceC Caution100% 220 ms–
/api/v1/compute/thermal-measurements/provenance-edge-auditC Caution100% 433 ms–
/api/v1/compute/thermal-measurements/record-sequence-diffC Caution100% 335 ms–
/api/v1/compute/thermal-measurements/reference-integrity-mapC Caution100% 313 ms–
/api/v1/compute/thermal-measurements/required-field-coverageC Caution100% 283 ms–
/api/v1/compute/thermal-measurements/revision-delta-mapC Caution100% 338 ms–
/api/v1/compute/thermal-measurements/schema-directionalityC Caution100% 332 ms–
/api/v1/compute/thermal-measurements/scope-boundary-auditC Caution100% 328 ms–
/api/v1/compute/thermal-measurements/source-coverage-mapC Caution100% 302 ms–
/api/v1/compute/thermal-measurements/timestamp-order-auditC Caution100% 219 ms–
/api/v1/compute/thermal-measurements/unit-label-consistencyC Caution100% 232 ms–
/api/v1/context/budgets/allocationC Caution100% 286 ms–

About www.mahastrategies.com

Is www.mahastrategies.com safe to pay?

61 of www.mahastrategies.com's endpoints are rated Proceed: reliable in monitoring with a stable price and payout wallet, and the best ones delivered in a real paid test. Grades are per endpoint, so look up the one your agent is about to pay.

How are these grades made?

Lumière PayCheck checks every endpoint about every 30 minutes: does it answer with a valid x402 quote, is the price and payout wallet stable. Then we pay some of them for real and check the response against what the listing promised. Failures are re-tested before they count. How it works.

Can my agent check www.mahastrategies.com before paying?

Yes, for free. Call check_payment (API or MCP) with the endpoint, amount and payTo from the 402 quote, and pay only if it returns allow. Check an endpoint now.

Do you run www.mahastrategies.com? Prove your endpoints work: get tested, check your setup, or add endpoints we're missing. Every seller's results are public, here and in the full catalog.