POST https://parallelmpp.dev/api/task
A run_id from POST /api/task is required before polling.
Parallel · Independent
Web search, extraction, async task execution, and machine-readable API discovery over MPP/Tempo.
GET https://parallelmpp.dev/api/task/:runId
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
Service health is aging because one or more endpoints have stale monitoring evidence.
Hourly score snapshots are appended whenever the derived health layer recomputes.
Documented reference price 0 USD is available, but no observed price history has been captured yet.
No observed challenge price history has been recorded yet for this endpoint.
Workflow evidence is aging: 1 monitored step(s) have stale probe data.
The latest normalized challenge data is stored here, including the new Solana-aware fields.
No documented session lifecycle has been synced for this endpoint yet.
POST https://parallelmpp.dev/api/task
A run_id from POST /api/task is required before polling.
GET https://parallelmpp.dev/api
GET /api explains the async create/poll workflow.
No challenge snapshots have been captured yet.
No extra notes recorded.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
The connected provider workflow is tracked, but some monitored workflow evidence is stale.
The workflow is documented, but no monitored runtime step has been verified yet.
The provider flow is usable, but at least one documented workflow step still relies on docs-only metadata.
Some documented workflow steps point to routes that are not yet captured as sibling endpoint records.
The workflow is documented, but no monitored runtime step has been verified yet.
Some documented workflow steps point to routes that are not yet captured as sibling endpoint records.
4 endpoint(s) in this service have stale monitoring evidence.
Multiple endpoint-level incidents are currently open for this service.
1 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
No open findings are currently recorded.