mahastrategies-com Webhooks API
Stripe payment confirmation (called by Stripe, documented for transparency).
Stripe payment confirmation (called by Stripe, documented for transparency).
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/mahastrategies-com:mahastrategies-com-webhooks-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Maha Strategies MPS Webhooks API
version: '0.1'
description: 'The Maha Provenance Standard (MPS) API runs claim-level provenance audits over prose. Every factual claim in a passage is excerpted, tagged (VERIFIED, SOURCED, BOUNDARY, ILLUSTRATIVE, UNVERIFIED), and returned with a rationale and a recommended action — so agents and editors can verify before they publish.
## Local bridge (CLI)
Install the open-source local bridge and point Claude Code, Cursor, or any MCP client at it:
```sh
npm install -g @mahastrategies/maha-mcp-bridge
maha login # verify and store your credential
maha serve # start the stdio MCP server
```
Raw rows and credentials stay local; only locally-redacted context reaches the agent''s cloud model.
## Authentication
Commercial endpoints use bearer credentials:
```
Authorization: Bearer mhaic_your_credential_here
```
Credentials are shown **exactly once** at purchase. Store them in a secret manager; never commit them, log them, or place them in URLs. Each credential is scoped to the MPS audit capability only — it cannot touch any other service. Lost credentials cannot be recovered, only replaced.
The free preflight endpoint (`POST /api/audit`) needs no credential and is limited per visitor per day.
## The credit system
Paid audits are prepaid. Each successful audit consumes one `mps_audit_invocation` credit; failed audits are refunded automatically in the same ledger.
When a credential runs out of credits, the API responds with **`402 Payment Required`**:
```json
{
"error": { "code": "payment_required", "message": "This prepaid credential has no audit credits remaining." },
"purchase": { "href": "/mps/audit-access", "checkoutEndpoint": "/api/mps-credits/checkout", "unit": "mps_audit_invocation" }
}
```
Treat `402` as a routine signal, not an error: follow `purchase.href` to buy another pack, or call the checkout endpoint programmatically. Balances live in an append-only double-entry ledger — every grant, consumption, refund, and manual correction is a permanent, hash-chained row.
## Idempotency and webhook resilience
**Requests**: every audit takes a `clientRequestId` you choose (8–120 characters). Retrying with the same id and the same text returns the original result with `idempotentReplay: true` — never a duplicate charge. The same id with *different* text returns `409 Conflict`. Safe retry loop: keep the same id until you get a terminal status.
**Payments**: Stripe webhooks are processed exactly once. Each event id is claimed atomically in the same database transaction that moves credits, so a redelivered webhook can never double-credit a balance — duplicates get `200 OK` with `"duplicate": true` and change nothing. A crash between claim and grant rolls both back together. You never need to reconcile double-grants; the ledger cannot express them.'
contact:
name: Maha Strategies
url: https://www.mahastrategies.com/contact
servers:
- url: https://www.mahastrategies.com
tags:
- name: Webhooks
description: Stripe payment confirmation (called by Stripe, documented for transparency).
paths:
/api/mps-credits/webhook:
post:
tags:
- Webhooks
operationId: stripeCreditsWebhook
summary: Stripe payment webhook (Stripe calls this — you never do)
description: Verifies the `Stripe-Signature` header (HMAC-SHA256, ±5-minute replay window) and processes checkout completions and refunds exactly once per Stripe event id.
parameters:
- name: Stripe-Signature
in: header
required: true
schema:
type: string
description: Stripe webhook signature (`t=…,v1=…`).
requestBody:
required: true
content:
application/json:
schema:
type: object
description: Raw Stripe event payload.
responses:
'200':
description: 'Event handled. Redeliveries of an already-processed event return `duplicate: true` and change nothing.'
content:
application/json:
schema:
type: object
required:
- received
properties:
received:
type: boolean
const: true
duplicate:
type: boolean
'400':
description: Invalid signature or malformed event.
content:
application/json:
schema:
type: object
properties:
error:
type: string
'503':
description: Ledger unavailable; Stripe will retry.
content:
application/json:
schema:
type: object
properties:
error:
type: string
components:
securitySchemes:
credential:
type: http
scheme: bearer
description: MPS client credential (`mhaic_…`), issued once at purchase.