Phareio Phare API

Name: Phare API
Brand: Phare API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer10 EndpointsREST

For Agents

Create and manage uptime monitors that check endpoint availability. Pause, resume, and configure HTTP monitors, and retrieve incident records when downtime occurs.

Install Jentic One Beta

Connect the Phare API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Phare API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Phare API.

Create HTTP uptime monitors to track endpoint availability and response times

Pause and resume monitors for maintenance windows without deletion

Retrieve incident records with downtime details and resolution status

GET STARTED

Start building with Phare API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Phare API for, with concrete tasks.

★ Automated Uptime Monitoring Setup

Create HTTP uptime monitors programmatically when deploying new services or endpoints. POST /uptime/monitors accepts URL, check interval, and alert configuration. Agents can automatically provision monitoring for each new microservice or API endpoint as part of the deployment pipeline, ensuring nothing goes unmonitored.

Create a new uptime monitor via POST /uptime/monitors with URL 'https://api.example.com/health', 60-second interval, and HTTP GET method

Maintenance Window Management

Pause monitors during planned maintenance to avoid false incident alerts, then resume them when maintenance completes. POST /uptime/monitors/{id}/pause stops checking temporarily, and POST /uptime/monitors/{id}/resume restarts monitoring. Agents can orchestrate this around deployment schedules automatically.

Pause monitor ID 42 via POST /uptime/monitors/42/pause before deployment, then resume it via POST /uptime/monitors/42/resume after health check passes

Incident Reporting and Analysis

Retrieve incident records to analyze downtime patterns, measure SLA compliance, or trigger escalation workflows. GET /uptime/incidents returns all detected incidents with timestamps, duration, and affected monitors. Agents can aggregate this data for weekly reliability reports or feed it into alerting pipelines.

Retrieve all incidents via GET /uptime/incidents, filter for the past 7 days, and calculate total downtime minutes per monitor for an SLA report

AI Agent Uptime Management via Jentic

AI agents discover and manage Phare uptime monitors through Jentic as part of infrastructure automation workflows. Agents search for monitoring capabilities by intent, receive operation schemas with Bearer auth handled, and create monitors or query incidents without manual integration. This enables self-healing infrastructure patterns.

Search Jentic for 'create an uptime monitor', load the POST /uptime/monitors schema, and execute with target URL and check interval parameters

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for phare api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/uptime/monitors

List all uptime monitors

POST

/uptime/monitors

Create a new monitor

GET

/uptime/monitors/{id}

Get a specific monitor

POST

/uptime/monitors/{id}/pause

Pause a monitor

POST

/uptime/monitors/{id}/resume

Resume a paused monitor

DELETE

/uptime/monitors/{id}

Delete a monitor

GET

/uptime/incidents

List all incidents

GET

/projects

List projects

GET

/uptime/monitors

List all uptime monitors

POST

/uptime/monitors

Create a new monitor

GET

/uptime/monitors/{id}

Get a specific monitor

POST

/uptime/monitors/{id}/pause

Pause a monitor

POST

/uptime/monitors/{id}/resume

Resume a paused monitor

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Phare Bearer API keys are stored encrypted in the Jentic vault. Agents receive scoped access without the raw key entering their working context. Project-scoped and org-scoped keys are both supported.

Intent-based discovery

Agents search by intent (e.g., 'create an uptime monitor') and Jentic returns matching Phare operations with schemas, enabling immediate monitor provisioning without reading API docs.

Time to first call

Direct Phare integration: under 1 day for auth and 10 endpoints. Through Jentic: under 1 hour — search, load schema, execute with managed credentials.

FAQs

Specific to using Phare API through Jentic.

Why is there no official OpenAPI spec for Phare API?

Phare does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Phare API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Phare API use?

The Phare API uses Bearer token authentication. API keys are generated from the Phare control panel and can be project-scoped (acting on a specific project) or organization-scoped (requiring project selection headers). Through Jentic, your API key is stored encrypted and agents never handle the raw token.

Can I pause monitors during maintenance?

Yes. POST /uptime/monitors/{id}/pause temporarily stops a monitor from checking. POST /uptime/monitors/{id}/resume restarts it. This prevents false incident alerts during planned maintenance windows without deleting and recreating the monitor.

How do I retrieve incident data through Jentic?

Search Jentic for 'list uptime incidents' to discover GET /uptime/incidents. Load the schema and execute to retrieve incident records including timestamps, affected monitors, and downtime duration. Use this data for SLA reporting or escalation logic.

What is the difference between project-scoped and organization-scoped API keys?

Project-scoped keys automatically target their assigned project for all operations. Organization-scoped keys require you to specify the target project via request headers, but allow access to multiple projects with a single key. GET /projects lists available projects for organization-scoped keys.

Phareio Phare API

Connect the Phare API to your agent

Capabilities

Start building with Phare API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs