Merit Systems · Service view
AI phone calls, dedicated phone numbers, and iMessage/FaceTime lookup — pay per request. Observed on MPPScan (7d): rank #4, 281 tx, $26.6 volume, 17 agents, seen 2h ago.
Manifest refresh updates matching endpoints, adds newly declared ones, and then queues reverification. Missing endpoints are left in place for safety instead of being auto-deleted.
Self-reported manifests published by owner-approved delegates. These updates are indexed for discovery and namespace lookups, but they do not replace stronger official or corroborated sources by themselves.
No delegate manifest publications have been indexed for this service yet.
No alternate registry records currently resolve to this service's public identity.
This service currently appears as a single-source public identity.
Hourly service-level snapshots are appended whenever endpoint/service health recomputes.
No observed service-level price history is available yet.
No observed service-level price history has been recorded yet.
Hourly Build 2 telemetry from provider-installed middleware. This is where revenue, conversion, latency, and agent traffic start compounding back into the registry.
No provider telemetry has been ingested for this service yet.
No endpoint-level analytics slices have been matched for this service yet.
No method-level telemetry yet.
No intent-level telemetry yet.
No agent cohorts have been derived for this service yet.
Trust distribution will appear once this service has recent agent traffic and trust history.
Strong recent payment history and the healthiest trust mix in the current traffic window.
Positive recent history, but still building toward stronger evidence and broader provider coverage.
Thin-file or watchlisted traffic that should usually stay under shadowing or small enforced rollouts first.
Traffic without enough shared history yet to earn a trust record.
Merit Systems · GET /api/jobs
Merit Systems · POST /api/inbox/messages/delete
Merit Systems · POST /api/inbox/cancel
Merit Systems · POST /api/inbox/update
Merit Systems · GET /api/inbox/status
Merit Systems · POST /api/subdomain/inbox/messages/delete
Merit Systems · POST /api/subdomain/inbox/delete
Merit Systems · POST /api/subdomain/inbox/update
7 of 7 route(s)
0 of 7 route(s)
0 of 7 route(s)
4 of 7 route(s)
0 of 7 route(s)
No approval or lease lifecycle events have been ingested yet.
Premium route class
Premium route class
Premium route class
Premium route class
Premium route class
Premium route class
Premium route class
Trust enforcement telemetry appears once providers start recording advisory, shadow, or enforced trust decisions through the analytics pipeline.
No analytics alerts are open for this service right now.
No recent analytics events have been recorded for this service yet.
This Build 2 slice accepts provider telemetry through a service-scoped ingest key and rolls it up hourly for revenue, conversion, latency, and agent-activity views.
7 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
7 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
7 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.
POST
https://stablephone.dev/api/call
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST
https://stablephone.dev/api/number/topup
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET
https://stablephone.dev/api/numbers
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET
https://stablephone.dev/api/lookup/status
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET
https://stablephone.dev/api/call/:id
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST
https://stablephone.dev/api/number
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST
https://stablephone.dev/api/lookup
The registry has not seen enough live runtime evidence yet to classify public access confidently.
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.