Lumière PayCheck Free API key

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/intel/scientific-dataset-records/revision-delta-mapC Caution100% 243 ms–
/api/v1/intel/scientific-dataset-records/schema-directionalityC Caution100% 277 ms–
/api/v1/intel/scientific-dataset-records/scope-boundary-auditC Caution100% 260 ms–
/api/v1/intel/scientific-dataset-records/source-coverage-mapC Caution100% 241 ms–
/api/v1/intel/scientific-dataset-records/timestamp-order-auditC Caution100% 235 ms–
/api/v1/intel/scientific-dataset-records/unit-label-consistencyC Caution100% 237 ms–
/api/v1/intel/trial-registry-records/condition-coverage-mapC Caution100% 250 ms–
/api/v1/intel/trial-registry-records/declared-bound-auditC Caution100% 296 ms–
/api/v1/intel/trial-registry-records/duplicate-record-identitiesC Caution100% 233 ms–
/api/v1/intel/trial-registry-records/export-semantic-parityC Caution100% 378 ms–
/api/v1/intel/trial-registry-records/identifier-crosswalk-auditC Caution100% 249 ms–
/api/v1/intel/trial-registry-records/missingness-cooccurrenceC Caution100% 240 ms–
/api/v1/intel/trial-registry-records/provenance-edge-auditC Caution100% 261 ms–
/api/v1/intel/trial-registry-records/record-sequence-diffC Caution100% 241 ms–
/api/v1/intel/trial-registry-records/reference-integrity-mapC Caution100% 286 ms–
/api/v1/intel/trial-registry-records/required-field-coverageC Caution100% 243 ms–
/api/v1/intel/trial-registry-records/revision-delta-mapC Caution100% 232 ms–
/api/v1/intel/trial-registry-records/schema-directionalityC Caution100% 236 ms–
/api/v1/intel/trial-registry-records/scope-boundary-auditC Caution100% 227 ms–
/api/v1/intel/trial-registry-records/source-coverage-mapC Caution100% 232 ms–
/api/v1/intel/trial-registry-records/timestamp-order-auditC Caution100% 244 ms–
/api/v1/intel/trial-registry-records/unit-label-consistencyC Caution100% 363 ms–
/api/v1/intel/trials/registry-statusC Caution100% 239 ms–
/api/v1/library/bibliographies/condition-coverage-mapC Caution100% 356 ms–
/api/v1/library/bibliographies/declared-bound-auditC Caution100% 310 ms–
/api/v1/library/bibliographies/duplicate-record-identitiesC Caution100% 301 ms–
/api/v1/library/bibliographies/export-semantic-parityC Caution100% 241 ms–
/api/v1/library/bibliographies/identifier-crosswalk-auditC Caution100% 256 ms–
/api/v1/library/bibliographies/missingness-cooccurrenceC Caution100% 228 ms–
/api/v1/library/bibliographies/provenance-edge-auditC Caution100% 235 ms–
/api/v1/library/bibliographies/record-sequence-diffC Caution100% 317 ms–
/api/v1/library/bibliographies/reference-integrity-mapC Caution100% 347 ms–
/api/v1/library/bibliographies/required-field-coverageC Caution100% 236 ms–
/api/v1/library/bibliographies/revision-delta-mapC Caution100% 235 ms–
/api/v1/library/bibliographies/schema-directionalityC Caution100% 303 ms–
/api/v1/library/bibliographies/scope-boundary-auditC Caution100% 252 ms–
/api/v1/library/bibliographies/source-coverage-mapC Caution100% 246 ms–
/api/v1/library/bibliographies/timestamp-order-auditC Caution100% 277 ms–
/api/v1/library/bibliographies/unit-label-consistencyC Caution100% 259 ms–
/api/v1/library/bibliography/resolve-doisC Caution100% 357 ms–
/api/v1/library/books/cross-book-conceptsC Caution100% 236 ms–
/api/v1/library/books/live-citation-recheckC Caution100% 288 ms–
/api/v1/library/citations/locator-conversionC Caution100% 220 ms–
/api/v1/library/edition-records/condition-coverage-mapC Caution100% 227 ms–
/api/v1/library/edition-records/declared-bound-auditC Caution100% 231 ms–
/api/v1/library/edition-records/duplicate-record-identitiesC Caution100% 231 ms–
/api/v1/library/edition-records/export-semantic-parityC Caution100% 234 ms–
/api/v1/library/edition-records/identifier-crosswalk-auditC Caution100% 232 ms–
/api/v1/library/edition-records/missingness-cooccurrenceC Caution100% 229 ms–
/api/v1/library/edition-records/provenance-edge-auditC Caution100% 227 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.