Merit Systems · Service certification
Service uncertified
This service has registered endpoints, but it does not currently have a meaningful public certification signal.
Service trust summary
Badge and embed
This service badge links back to a breakdown of endpoint-level proof, so the trust signal stays auditable instead of collapsing to a marketing claim.
Endpoint proof breakdown
POST /api/subdomain/send
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/signers
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/update
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET /api/subdomain/status
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/list
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/delete
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/messages
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/messages/delete
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/topup/quarter
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/send
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/update
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/messages/read
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/messages/delete
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/send
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/buy
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/create
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/update
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/subdomain/inbox/messages/read
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/buy
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/topup
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/topup/year
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
GET /api/inbox/status
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/cancel
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
POST /api/inbox/messages
Draft
Endpoint health is mostly based on declared workflow metadata because runtime monitoring is still incomplete.
Active service incidents
24 endpoint(s) in this service still rely mostly on documented metadata instead of runtime proof.