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/context/contract-amendments/condition-coverage-mapC Caution100% 270 ms–
/api/v1/context/contract-amendments/declared-bound-auditC Caution100% 219 ms–
/api/v1/context/contract-amendments/duplicate-record-identitiesC Caution100% 261 ms–
/api/v1/context/contract-amendments/export-semantic-parityC Caution100% 300 ms–
/api/v1/context/contract-amendments/identifier-crosswalk-auditC Caution100% 209 ms–
/api/v1/context/contract-amendments/missingness-cooccurrenceC Caution100% 255 ms–
/api/v1/context/contract-amendments/provenance-edge-auditC Caution100% 235 ms–
/api/v1/context/contract-amendments/record-sequence-diffC Caution100% 211 ms–
/api/v1/context/contract-amendments/reference-integrity-mapC Caution100% 225 ms–
/api/v1/context/contract-amendments/required-field-coverageC Caution100% 265 ms–
/api/v1/context/contract-amendments/revision-delta-mapC Caution100% 227 ms–
/api/v1/context/contract-amendments/schema-directionalityC Caution100% 227 ms–
/api/v1/context/contract-amendments/scope-boundary-auditC Caution100% 230 ms–
/api/v1/context/contract-amendments/source-coverage-mapC Caution100% 223 ms–
/api/v1/context/contract-amendments/timestamp-order-auditC Caution100% 233 ms–
/api/v1/context/contract-amendments/unit-label-consistencyC Caution100% 220 ms–
/api/v1/context/evidence/conflictsC Caution100% 187 ms–
/api/v1/context/evidence/coverage-driftC Caution100% 246 ms–
/api/v1/context/evidence/frame-compatibilityC Caution100% 207 ms–
/api/v1/context/evidence/manifestC Caution100% 210 ms–
/api/v1/context/evidence/scopeC Caution100% 224 ms–
/api/v1/context/evidence/version-selectionC Caution100% 260 ms–
/api/v1/context/governed-verificationC Caution100% 230 ms–
/api/v1/context/incident-notes/condition-coverage-mapC Caution100% 238 ms–
/api/v1/context/incident-notes/declared-bound-auditC Caution100% 228 ms–
/api/v1/context/incident-notes/duplicate-record-identitiesC Caution100% 241 ms–
/api/v1/context/incident-notes/export-semantic-parityC Caution100% 310 ms–
/api/v1/context/incident-notes/identifier-crosswalk-auditC Caution100% 357 ms–
/api/v1/context/incident-notes/missingness-cooccurrenceC Caution100% 261 ms–
/api/v1/context/incident-notes/provenance-edge-auditC Caution100% 279 ms–
/api/v1/context/incident-notes/record-sequence-diffC Caution100% 357 ms–
/api/v1/context/incident-notes/reference-integrity-mapC Caution100% 267 ms–
/api/v1/context/incident-notes/required-field-coverageC Caution100% 232 ms–
/api/v1/context/incident-notes/revision-delta-mapC Caution100% 233 ms–
/api/v1/context/incident-notes/schema-directionalityC Caution100% 237 ms–
/api/v1/context/incident-notes/scope-boundary-auditC Caution100% 236 ms–
/api/v1/context/incident-notes/source-coverage-mapC Caution100% 224 ms–
/api/v1/context/incident-notes/timestamp-order-auditC Caution100% 230 ms–
/api/v1/context/incident-notes/unit-label-consistencyC Caution100% 223 ms–
/api/v1/context/legacy/context-budget-ladderC Caution100% 239 ms–
/api/v1/context/legacy/context-compressionC Caution100% 242 ms–
/api/v1/context/legacy/deep-context-evaluationC Caution100% 250 ms–
/api/v1/context/legacy/evidence-retention-matrixC Caution100% 222 ms–
/api/v1/context/meeting-records/condition-coverage-mapC Caution100% 222 ms–
/api/v1/context/meeting-records/declared-bound-auditC Caution100% 217 ms–
/api/v1/context/meeting-records/duplicate-record-identitiesC Caution100% 222 ms–
/api/v1/context/meeting-records/export-semantic-parityC Caution100% 208 ms–
/api/v1/context/meeting-records/identifier-crosswalk-auditC Caution100% 241 ms–
/api/v1/context/meeting-records/missingness-cooccurrenceC Caution100% 231 ms–
/api/v1/context/meeting-records/provenance-edge-auditC Caution100% 231 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.