Sentivel bronze

sentivel.com

“Manage status pages, uptime monitors, incidents, on-call schedules, and escalation policies over MCP or REST.

https://sentivel.com/.well-known/agent-card.json its card

🇺🇸 US · Amazon.com, Inc. Checked 22h ago

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Let's Encrypt domain-validated
Valid until 3 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.
DANE / TLSA: Not verified
Discovery: Well-known document
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
First seen: 5 Aug 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇺🇸 US · Amazon.com, Inc. (AS16509)
Last checked: 22h ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of sentivel.com controls every word below.

Connect to the Sentivel MCP server

Connect an agent to Sentivel's hosted MCP server and authenticate with OAuth or a token.

Call the Sentivel REST API

Authenticate against the Sentivel REST API and discover its endpoints from the OpenAPI spec.

Publish a Sentivel status page

Create a status page, add components, and attach uptime monitors so the page reflects real state.

Run an incident in Sentivel

Open an incident, post updates, acknowledge it, and resolve it, including reading the escalation ladder.

Map dependencies on third-party providers

Link your components to the providers they rely on so an upstream incident auto-posts an advisory on your status page.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: Sentivel Ltd — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.0.0
Auth schemes: bearer oauth2
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
defaultInputModesdefaultOutputModes

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Agent card: https://sentivel.com/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.