API Platform

Platform Health Feed

A product-facing operational feed that exposes usage, API governance, billing readiness, webhook delivery state, report delivery policy, and integration health.

Best for: SEO software platforms, CMS plugins, client portals, and internal product teams.

Try this report API docs All examples

Platform Health Feed API Platform

36Credits Used

0.14%Quota

WarnStripe

OKAPI

Item	Status	Evidence
API governance	OK	Required read scopes covered by active keys.
Stripe	Warn	Price IDs and webhook secret must be configured.
Report delivery	Review	External delivery remains approval-gated.

What It Includes

Usage, credits, quota posture, plan status, and billing governance
API request log health, scope coverage, key posture, and endpoint readiness
Webhook delivery planning and report governance status
Integration readiness for GSC, schema refresh, account storage, and jobs

How It Is Generated

Usage ledger and billing governance files
API governance and request log status
Webhook delivery policy and report delivery policy
Secrets, retention, artifact, and account-storage readiness

API Inputs

/v1/usage/v1/api/governance/v1/billing/governance/v1/webhooks/delivery-policy/v1/reports/governance

MCP Uses

Ask whether a workspace is ready for live billing.
Explain which launch gates are still blocked.
Summarize API, webhook, and reporting health for an operator.

Ways People Use It

SaaS Readiness Check Platform owner

Review billing, storage, API, webhook, report, and secret readiness before inviting paid users.

Launch blockers are visible in one operational feed.

Support Triage Support operator

Check whether a customer issue is caused by API scopes, billing state, missing GSC, or failed jobs.

Support can answer with actual workspace state.

Embedded Product Health Product team

Expose API governance and usage state inside another SEO product or portal.

The product can show customers whether evidence is fresh, limited, or blocked.

Evidence Contract

The live API returns the issue plus the evidence around it: what happened, where it happened, when it was observed, why it matters, and how to act.

Question	Where It Comes From	Example
What	Issue ID, severity, message, schema, crawl, or GSC state	`jsonld_invalid`, `schema_missing`, `noindex_detected`
Where	URL, site, client, final URL, JSON-LD block index, or endpoint row	`/pricing`, block `0`
When	`generated_at`, `fetched_at`, event timestamps, and history metrics	Last observed during the current refresh.
Why	Evidence fields, parse errors, HTTP status, GSC verdict, and crawl facts	JSON parse error, noindex header, sitemap leak, or canonical conflict.
How	Recommended actions and MCP or report prompts	Fix malformed JSON-LD, remove noindex, update sitemap, or consolidate canonical.

For malformed JSON-LD, the API records the affected page, fetch time, invalid block index, parser error, issue severity, and recommended action. It intentionally avoids storing raw page payloads unless a future redacted evidence store is enabled.

Example API Flow

curl.exe -H "Authorization: Bearer YOUR_API_TOKEN" https://indexpulseapi.com/v1/usage

MCP prompt example:
"Ask whether a workspace is ready for live billing."