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/intel/materials/property-snapshotC Caution100% 233 ms–
/api/v1/intel/procurement-notices/condition-coverage-mapC Caution100% 262 ms–
/api/v1/intel/procurement-notices/declared-bound-auditC Caution100% 221 ms–
/api/v1/intel/procurement-notices/duplicate-record-identitiesC Caution100% 250 ms–
/api/v1/intel/procurement-notices/export-semantic-parityC Caution100% 225 ms–
/api/v1/intel/procurement-notices/identifier-crosswalk-auditC Caution100% 224 ms–
/api/v1/intel/procurement-notices/missingness-cooccurrenceC Caution100% 236 ms–
/api/v1/intel/procurement-notices/provenance-edge-auditC Caution100% 241 ms–
/api/v1/intel/procurement-notices/record-sequence-diffC Caution100% 229 ms–
/api/v1/intel/procurement-notices/reference-integrity-mapC Caution100% 233 ms–
/api/v1/intel/procurement-notices/required-field-coverageC Caution100% 233 ms–
/api/v1/intel/procurement-notices/revision-delta-mapC Caution100% 237 ms–
/api/v1/intel/procurement-notices/schema-directionalityC Caution100% 234 ms–
/api/v1/intel/procurement-notices/scope-boundary-auditC Caution100% 224 ms–
/api/v1/intel/procurement-notices/source-coverage-mapC Caution100% 255 ms–
/api/v1/intel/procurement-notices/timestamp-order-auditC Caution100% 222 ms–
/api/v1/intel/procurement-notices/unit-label-consistencyC Caution100% 238 ms–
/api/v1/intel/publication-records/condition-coverage-mapC Caution100% 230 ms–
/api/v1/intel/publication-records/declared-bound-auditC Caution100% 228 ms–
/api/v1/intel/publication-records/duplicate-record-identitiesC Caution100% 228 ms–
/api/v1/intel/publication-records/export-semantic-parityC Caution100% 206 ms–
/api/v1/intel/publication-records/identifier-crosswalk-auditC Caution100% 208 ms–
/api/v1/intel/publication-records/missingness-cooccurrenceC Caution100% 226 ms–
/api/v1/intel/publication-records/provenance-edge-auditC Caution100% 232 ms–
/api/v1/intel/publication-records/record-sequence-diffC Caution100% 259 ms–
/api/v1/intel/publication-records/reference-integrity-mapC Caution100% 233 ms–
/api/v1/intel/publication-records/required-field-coverageC Caution100% 245 ms–
/api/v1/intel/publication-records/revision-delta-mapC Caution100% 238 ms–
/api/v1/intel/publication-records/schema-directionalityC Caution100% 242 ms–
/api/v1/intel/publication-records/scope-boundary-auditC Caution100% 284 ms–
/api/v1/intel/publication-records/source-coverage-mapC Caution100% 238 ms–
/api/v1/intel/publication-records/timestamp-order-auditC Caution100% 229 ms–
/api/v1/intel/publication-records/unit-label-consistencyC Caution100% 235 ms–
/api/v1/intel/publications/correction-impactC Caution100% 247 ms–
/api/v1/intel/publications/declared-fundingC Caution100% 241 ms–
/api/v1/intel/publications/declared-relationsC Caution100% 278 ms–
/api/v1/intel/publications/updatesC Caution100% 271 ms–
/api/v1/intel/quantum/hardware-snapshotC Caution100% 225 ms–
/api/v1/intel/research/evidence-briefC Caution100% 226 ms–
/api/v1/intel/research/opportunity-comparisonC Caution100% 227 ms–
/api/v1/intel/scientific-dataset-records/condition-coverage-mapC Caution100% 241 ms–
/api/v1/intel/scientific-dataset-records/declared-bound-auditC Caution100% 217 ms–
/api/v1/intel/scientific-dataset-records/duplicate-record-identitiesC Caution100% 225 ms–
/api/v1/intel/scientific-dataset-records/export-semantic-parityC Caution100% 242 ms–
/api/v1/intel/scientific-dataset-records/identifier-crosswalk-auditC Caution100% 271 ms–
/api/v1/intel/scientific-dataset-records/missingness-cooccurrenceC Caution100% 227 ms–
/api/v1/intel/scientific-dataset-records/provenance-edge-auditC Caution100% 243 ms–
/api/v1/intel/scientific-dataset-records/record-sequence-diffC Caution100% 229 ms–
/api/v1/intel/scientific-dataset-records/reference-integrity-mapC Caution100% 241 ms–
/api/v1/intel/scientific-dataset-records/required-field-coverageC Caution100% 246 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.