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/meeting-records/record-sequence-diffC Caution100% 219 ms–
/api/v1/context/meeting-records/reference-integrity-mapC Caution100% 220 ms–
/api/v1/context/meeting-records/required-field-coverageC Caution100% 211 ms–
/api/v1/context/meeting-records/revision-delta-mapC Caution100% 226 ms–
/api/v1/context/meeting-records/schema-directionalityC Caution100% 234 ms–
/api/v1/context/meeting-records/scope-boundary-auditC Caution100% 235 ms–
/api/v1/context/meeting-records/source-coverage-mapC Caution100% 261 ms–
/api/v1/context/meeting-records/timestamp-order-auditC Caution100% 271 ms–
/api/v1/context/meeting-records/unit-label-consistencyC Caution100% 249 ms–
/api/v1/context/policies/version-comparisonC Caution100% 230 ms–
/api/v1/context/policy-excerpts/condition-coverage-mapC Caution100% 272 ms–
/api/v1/context/policy-excerpts/declared-bound-auditC Caution100% 244 ms–
/api/v1/context/policy-excerpts/duplicate-record-identitiesC Caution100% 295 ms–
/api/v1/context/policy-excerpts/export-semantic-parityC Caution100% 290 ms–
/api/v1/context/policy-excerpts/identifier-crosswalk-auditC Caution100% 298 ms–
/api/v1/context/policy-excerpts/missingness-cooccurrenceC Caution100% 265 ms–
/api/v1/context/policy-excerpts/provenance-edge-auditC Caution100% 256 ms–
/api/v1/context/policy-excerpts/record-sequence-diffC Caution100% 247 ms–
/api/v1/context/policy-excerpts/reference-integrity-mapC Caution100% 303 ms–
/api/v1/context/policy-excerpts/required-field-coverageC Caution100% 269 ms–
/api/v1/context/policy-excerpts/revision-delta-mapC Caution100% 227 ms–
/api/v1/context/policy-excerpts/schema-directionalityC Caution100% 244 ms–
/api/v1/context/policy-excerpts/scope-boundary-auditC Caution100% 275 ms–
/api/v1/context/policy-excerpts/source-coverage-mapC Caution100% 245 ms–
/api/v1/context/policy-excerpts/timestamp-order-auditC Caution100% 258 ms–
/api/v1/context/policy-excerpts/unit-label-consistencyC Caution100% 262 ms–
/api/v1/context/retrieval/cluster-comparisonC Caution100% 270 ms–
/api/v1/context/retrieval/packing-displacementC Caution100% 224 ms–
/api/v1/context/retrieval/recovery-regressionC Caution100% 273 ms–
/api/v1/context/source-packs/condition-coverage-mapC Caution100% 276 ms–
/api/v1/context/source-packs/declared-bound-auditC Caution100% 229 ms–
/api/v1/context/source-packs/duplicate-record-identitiesC Caution100% 301 ms–
/api/v1/context/source-packs/export-semantic-parityC Caution100% 229 ms–
/api/v1/context/source-packs/identifier-crosswalk-auditC Caution100% 317 ms–
/api/v1/context/source-packs/missingness-cooccurrenceC Caution100% 241 ms–
/api/v1/context/source-packs/provenance-edge-auditC Caution100% 238 ms–
/api/v1/context/source-packs/record-sequence-diffC Caution100% 361 ms–
/api/v1/context/source-packs/reference-integrity-mapC Caution100% 261 ms–
/api/v1/context/source-packs/required-field-coverageC Caution100% 303 ms–
/api/v1/context/source-packs/revision-delta-mapC Caution100% 320 ms–
/api/v1/context/source-packs/schema-directionalityC Caution100% 274 ms–
/api/v1/context/source-packs/scope-boundary-auditC Caution100% 274 ms–
/api/v1/context/source-packs/source-coverage-mapC Caution100% 267 ms–
/api/v1/context/source-packs/timestamp-order-auditC Caution100% 242 ms–
/api/v1/context/source-packs/unit-label-consistencyC Caution100% 186 ms–
/api/v1/context/study-notes/condition-coverage-mapC Caution100% 251 ms–
/api/v1/context/study-notes/declared-bound-auditC Caution100% 255 ms–
/api/v1/context/study-notes/duplicate-record-identitiesC Caution100% 243 ms–
/api/v1/context/study-notes/export-semantic-parityC Caution100% 251 ms–
/api/v1/context/study-notes/identifier-crosswalk-auditC Caution100% 243 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.