How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
usewrit-app

usewrit-app Monitors API

Page monitors (the `targets` table), device check capacity, and change history.

Documentation Provider Profile APIs.io OpenAPI GitHub

usewrit-app Monitors API is one of 17 APIs that usewrit-app publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Monitors. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 9 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 2 base URLs: http://127.0.0.1:8131, https://127.0.0.1:8132.

9 operations 6 paths 12 schemas 1 DELETE5 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.usewrit.app
Authentication
HTTP Bearer
License
MIT
Resource Areas
1

Authentication & Security 1

usewrit-app Monitors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Every route (including /v1/agent and /v1/health) requires Authorization: Bearer . Token families: - wlt… — the runtime token from runtime.json (full access, us…

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 1 DELETE, 5 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Monitors 9

Page monitors (the targets table), device check capacity, and change history.

GET
/v1/monitors
List monitors
listMonitors 2 params → 200401
POST
/v1/monitors
Create a monitor
createMonitor body → 200400401409
GET
/v1/monitors/capacity
Device check-capacity meter
getMonitorCapacity → 200401
GET
/v1/monitors/{id}
Get one monitor
getMonitor 1 param → 200401404
PATCH
/v1/monitors/{id}
Update a monitor
updateMonitor 1 param body → 200400401404409
DELETE
/v1/monitors/{id}
Delete a monitor
deleteMonitor 1 param → 200401404
POST
/v1/monitors/{id}/run
Run a monitor check now
runMonitor 1 param → 200401404
GET
/v1/monitors/{id}/changes
Change + uptime history of a monitor
listMonitorChanges 3 params → 200401404
GET
/v1/changes/recent
Recent changes across all monitors
listRecentChanges 1 param → 200401

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are Monitor (43 properties), MonitorCreate (28 properties), MonitorUpdate (27 properties), Change (13 properties). Each schema is shown below with its type and property counts.

CheckOutcome
object
Outcome of checking a single target (monitor::CheckOutcome). Optional fields are OMITTED (not null) when absent. Serialization failure degrades to {"monitorid"…
5 properties 2 required
MonitorCreate
object
Create body (store::targets::NewTarget). Flag fields accept booleans or 0/1 integers; numeric fields also accept numeric strings; setupsteps / onchangeconditio…
28 properties 1 required
Error
object
The daemon's domain error body. NOTE: some 4xx responses (axum framework rejections) are text/plain instead of this JSON shape. Certain codes attach extra fiel…
2 properties 2 required
DeviceCapacityError
The 409 body for a monitor create/update that would exceed the machine's sustainable checks/min budget (code: "devicecapacity").
MonitorUpdate
object
Partial PATCH body (store::targets::TargetUpdate) — same flexible field shapes as create, everything optional (COALESCE semantics).
27 properties
CapacitySnapshot
object
Device check-capacity meter (scheduler::capacity::CapacitySnapshot).
5 properties 5 required
UptimeCheck
object
One up/down + SSL sample (store::uptimechecks::UptimeCheck).
12 properties 4 required
DispatchOutcome
object
Automation dispatch tally for one detected change.
3 properties 3 required
RecentChange
object
One enriched cross-monitor change (store::changes::RecentChange).
8 properties 5 required
MonitorHistory
object
Paginated change + uptime history (GET /v1/monitors/{id}/changes).
6 properties 6 required
Change
object
One content-diff history row (store::changes::Change).
13 properties 5 required
Monitor
object
A monitor (targets row). setupsteps is credential-REDACTED on every response: its credentials sub-object is replaced with the sentinel string «redacted» (an un…
43 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

usewrit-app-monitors-api-openapi.yml Raw ↑

Other APIs usewrit-app publishes across the network.

usewrit-app Agent API
AE Profile APIs.io
usewrit-app Automations API
AE Profile APIs.io
usewrit-app Cloud API
AE Profile APIs.io
usewrit-app Crawl API
AE Profile APIs.io
usewrit-app Data API
AE Profile APIs.io
usewrit-app Datasets API
AE Profile APIs.io
usewrit-app Extractors API
AE Profile APIs.io
usewrit-app Files API
AE Profile APIs.io
usewrit-app Keys API
AE Profile APIs.io
usewrit-app Personas API
AE Profile APIs.io
usewrit-app Runs API
AE Profile APIs.io
usewrit-app Secrets API
AE Profile APIs.io
#Monitors
← Back to U APIs
API Details
ID
usewrit-app:usewrit-app-monitors-api
Base URL
https://api.usewrit.app
Docs
https://usewrit.app/docs/api
Provider
usewrit-app
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=usewrit-app-monitors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/usewrit-app-monitors-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of usewrit-app Monitors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.