VergeSense

VergeSense is the occupancy intelligence platform for corporate real estate and workplace teams. It combines first-party AI-powered area, entryway and infinity sensors with a cloud analytics platform (Meridian, including a Large Spatial Model) to measure how buildings, floors, neighborhoods and individual spaces are actually used. The public VergeSense API is a key-authenticated REST surface at api.vergesense.com covering buildings, floors, spaces, space types, detections, threshold crossings, hourly and aggregate occupancy metrics, hardware inventory (sensors and gateways), a Predict API built on the Large Spatial Model, and a fully managed webhook subscription surface that pushes space_report, space_availability and motion_detected events to customer endpoints. Collection responses follow the JSON:API specification, timestamps are ISO 8601, and the API is date-versioned (YYYY-MM-DD) via the vs-version request header. VergeSense also operates an OAuth-protected remote MCP server at mcp.vergesense.com for agent access.

VergeSense publishes 7 API contracts indexed on the APIs.io network, including Buildings API, Hardware API, Metrics API, and 4 more. Tagged areas include Occupancy Intelligence, Workplace Analytics, Corporate Real Estate, PropTech, and IoT Sensors.

The VergeSense catalog on APIs.io includes 1 event-driven AsyncAPI specification.

VergeSense’s developer surface includes documentation, API reference, getting-started guide, changelog, engineering blog, support, signup flow, and 29 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.8/100 developing ▬ flat Agent 51/100 agent ready Front door AI 3/6 light Heartbeat 50/100 alive Full breakdown ↓
scored 2026-11-01 · rubric v0.26.0 · Show this score on your site →

1 published contract 1 MCP Servers 3 Agent Skills

Occupancy IntelligenceWorkplace AnalyticsCorporate Real EstatePropTech IoT SensorsBuilding DataSpace Utilization Facilities Management Smart Buildings Webhook MCP JSON:API

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Facilities Management

BC-700

MetricsPredictSpaces

GET /spaces GET /spaces/detections GET /spaces/thresholds/crossings GET /spaces/types

Kin Score

Kin Score How this is scored →
scored 2026-11-01 · rubric v0.26.0

Composite quality — 51.8/100 · developing

Contract Quality 11.9 / 19

Developer Ergonomics 9.6 / 15

Access Clarity 3.2 / 15

Operational Transparency 5.4 / 10

Contract Governance 1.6 / 9

Discoverability 5.6 / 8

Regulatory Posture 5.1 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 51/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 0 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vergesense/"><img src="https://apis.io/badge/vergesense/card.svg" alt="VergeSense on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Contract Quality scores 63.2 — up to +9.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/vergesense/apis.yml: open an issue on github.com/api-evangelist/vergesense to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Building Automation (HVAC, BACnet, KNX, smart buildings)	standard	19.4 (thin)	-	-
ServiceNow Store (partner apps + ServiceNow Certified App)	standard	19.4 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 6

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

JSON:API

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

VergeSense Buildings API

The Buildings API from VergeSense — 3 operation(s) for buildings.

VergeSense Hardware API

The Hardware API from VergeSense — 2 operation(s) for hardware.

VergeSense Metrics API

The Metrics API from VergeSense — 13 operation(s) for metrics.

VergeSense Predict API

The Predict API from VergeSense — 3 operation(s) for predict.

VergeSense Sensors API

The Sensors API from VergeSense — 3 operation(s) for sensors.

VergeSense Spaces API

The Spaces API from VergeSense — 4 operation(s) for spaces.

VergeSense Webhooks API

The Webhooks API from VergeSense — 6 operation(s) for webhooks.

Scroll for all 7

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

VergeSense MCP Server

VergeSense operates a first-party remote MCP server on its own dedicated subdomain. It is not a derived candidate: an anonymous JSON-RPC POST of tools/list returns HTTP 401 with...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

vergesense-manage-event-webhook

AGENT SKILL

vergesense-portfolio-utilization-report

AGENT SKILL

vergesense-predict-space-demand

AGENT SKILL

Pricing Plans 1

Published pricing tiers and plan structures.

Vergesense Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Vergesense Rate Limits

1 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Vergesense Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Vergesense Webhooks

ASYNCAPI

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Vergesense Api Overlay

10 actions · documentation · vergesense-api-openapi.json

GENERATED

Examples 1

Example request and response payloads for these APIs.

Vergesense Api Examples

3 fields

EXAMPLE

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vergesense Authentication

apiKey/oauth2 · 2 schemes

SECURITY

Vergesense Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Vergesense Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

WellKnown

MCPServer

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Webhooks

Build 5

SDKs, sample code, and the tooling you integrate with

Postman

Postman

GitHubOrganization

Examples

Packages

ToolCrosswalk

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 5

Status, limits, changes, and where to get help

ChangeLog

Support

RateLimits

Deprecation

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: vergesense
name: VergeSense
description: VergeSense is the occupancy intelligence platform for corporate real estate and workplace teams. It combines
  first-party AI-powered area, entryway and infinity sensors with a cloud analytics platform (Meridian, including a Large
  Spatial Model) to measure how buildings, floors, neighborhoods and individual spaces are actually used. The public VergeSense
  API is a key-authenticated REST surface at api.vergesense.com covering buildings, floors, spaces, space types, detections,
  threshold crossings, hourly and aggregate occupancy metrics, hardware inventory (sensors and gateways), a Predict API built
  on the Large Spatial Model, and a fully managed webhook subscription surface that pushes space_report, space_availability
  and motion_detected events to customer endpoints. Collection responses follow the JSON:API specification, timestamps are
  ISO 8601, and the API is date-versioned (YYYY-MM-DD) via the vs-version request header. VergeSense also operates an OAuth-protected
  remote MCP server at mcp.vergesense.com for agent access.
image: https://www.vergesense.com/hubfs/assets/logo/vergesense-logo--color.png
url: https://raw.githubusercontent.com/api-evangelist/vergesense/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-02'
modified: '2026-09-02'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Occupancy Intelligence
- Workplace Analytics
- Corporate Real Estate
- PropTech
- IoT Sensors
- Building Data
- Space Utilization
- Facilities Management
- Smart Buildings
- Webhook
- MCP
- JSON:API
tags_raw:
- Occupancy Intelligence
- Workplace Analytics
- Corporate Real Estate
- PropTech
- IoT Sensors
- Building Data
- Space Utilization
- Facilities Management
- Smart Buildings
- Webhooks
- MCP
- JSON:API
apis:
- aid: vergesense:vergesense-buildings-api
  name: VergeSense Buildings API
  description: The Buildings API from VergeSense — 3 operation(s) for buildings.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Buildings
  properties:
  - type: OpenAPI
    url: openapi/vergesense-buildings-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-hardware-api
  name: VergeSense Hardware API
  description: The Hardware API from VergeSense — 2 operation(s) for hardware.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Hardware
  properties:
  - type: OpenAPI
    url: openapi/vergesense-hardware-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-metrics-api
  name: VergeSense Metrics API
  description: The Metrics API from VergeSense — 13 operation(s) for metrics.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Metrics
  properties:
  - type: OpenAPI
    url: openapi/vergesense-metrics-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-predict-api
  name: VergeSense Predict API
  description: The Predict API from VergeSense — 3 operation(s) for predict.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Predict
  properties:
  - type: OpenAPI
    url: openapi/vergesense-predict-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-sensors-api
  name: VergeSense Sensors API
  description: The Sensors API from VergeSense — 3 operation(s) for sensors.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Sensors
  properties:
  - type: OpenAPI
    url: openapi/vergesense-sensors-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-spaces-api
  name: VergeSense Spaces API
  description: The Spaces API from VergeSense — 4 operation(s) for spaces.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Spaces
  - Space
  tags_raw:
  - Spaces
  - Space
  properties:
  - type: OpenAPI
    url: openapi/vergesense-spaces-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
- aid: vergesense:vergesense-webhooks-api
  name: VergeSense Webhooks API
  description: The Webhooks API from VergeSense — 6 operation(s) for webhooks.
  humanURL: https://vergesense.readme.io/reference/reference-getting-started
  baseURL: https://api.vergesense.com
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/vergesense-webhooks-api-openapi.yml
  - type: Documentation
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: APIReference
    url: https://vergesense.readme.io/reference/buildings-1
  - type: GettingStarted
    url: https://vergesense.readme.io/reference/reference-getting-started
  - type: Postman
    url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
  - type: Authentication
    url: authentication/vergesense-authentication.yml
  - type: RateLimits
    url: rate-limits/vergesense-rate-limits.yml
  - type: ErrorCatalog
    url: errors/vergesense-problem-types.yml
  - type: Examples
    url: examples/vergesense-api-examples.json
  - type: Webhooks
    url: asyncapi/vergesense-webhooks.yml
  - type: DataModel
    url: data-model/vergesense-data-model.yml
  - type: Conventions
    url: conventions/vergesense-conventions.yml
  - type: ChangeLog
    url: changelog/vergesense-changelog.yml
  - type: ToolCrosswalk
    url: mcp/vergesense-tool-crosswalk.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/vergesense-capability-edges.yml
  name: VergeSense Business Capability Map
- type: Overlay
  url: overlays/vergesense-api-overlay.yaml
- type: Website
  url: https://www.vergesense.com/
- type: DeveloperPortal
  url: https://vergesense.readme.io/
- type: Documentation
  url: https://vergesense.readme.io/reference/reference-getting-started
- type: APIReference
  url: https://vergesense.readme.io/reference/buildings-1
- type: GettingStarted
  url: https://vergesense.readme.io/reference/reference-getting-started
- type: Postman
  url: https://documenter.getpostman.com/view/6835591/2s9Y5Wx3QL
- type: ChangeLog
  url: https://headwayapp.co/vergesense-changelog/
- type: Blog
  url: https://www.vergesense.com/resources/blog
- type: Support
  url: https://support.vergesense.com/hc/en-us
- type: SignUp
  url: https://cloud.vergesense.com/
- type: Login
  url: https://cloud.vergesense.com/
- type: TermsOfService
  url: https://www.vergesense.com/legal
- type: PrivacyPolicy
  url: https://www.vergesense.com/privacy-policy
- type: GitHubOrganization
  url: https://github.com/vergesense
- type: Authentication
  url: authentication/vergesense-authentication.yml
- type: OAuthScopes
  url: scopes/vergesense-scopes.yml
- type: RateLimits
  url: rate-limits/vergesense-rate-limits.yml
- type: ErrorCatalog
  url: errors/vergesense-problem-types.yml
- type: Examples
  url: examples/vergesense-api-examples.json
- type: Conventions
  url: conventions/vergesense-conventions.yml
- type: Lifecycle
  url: lifecycle/vergesense-lifecycle.yml
- type: Deprecation
  url: lifecycle/vergesense-lifecycle.yml
- type: ChangeLog
  url: changelog/vergesense-changelog.yml
- type: Conformance
  url: conformance/vergesense-conformance.yml
- type: DataModel
  url: data-model/vergesense-data-model.yml
- type: Webhooks
  url: asyncapi/vergesense-webhooks.yml
- type: Packages
  url: packages/vergesense-packages.yml
- type: Plans
  url: plans/vergesense-plans-pricing.yml
- type: LLMsTxt
  url: llms/vergesense-llms.txt
- type: WellKnown
  url: well-known/vergesense-well-known.yml
- type: MCPServer
  url: mcp/vergesense-mcp.yml
- type: ToolCrosswalk
  url: mcp/vergesense-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/vergesense-domain-security.yml
x-enrichment:
  date: '2026-09-02'
  status: enriched
  artifacts_added: 26
  pass: local-v1

VergeSense API — frequently asked questions

Does VergeSense have an API?

Yes. APIs.io lists 7 APIs from VergeSense, including VergeSense Buildings API, VergeSense Hardware API and VergeSense Metrics API, and 4 more.

Is there an OpenAPI specification for the VergeSense API?

Yes. APIs.io indexes 7 OpenAPI specifications for VergeSense, each linked for download from this page.

How do I authenticate with the VergeSense API?

VergeSense documents its authentication (apiKey/oauth2 · 2 schemes). The details are profiled on APIs.io as Vergesense Authentication.

Does VergeSense have an MCP server?

Yes. APIs.io lists 1 MCP server for VergeSense: VergeSense operates a first-party remote MCP server on its own dedicated subdomain. It is not a derived candidate: an anonymous JSON-RPC POST of tools/list returns HTTP 401 with an RFC 9728 WWW-Authen

Is the VergeSense API ready for AI agents?

VergeSense has a Kin Score of 51.8 out of 100 (developing) and an Agent Readiness score of 50.9 (agent-ready), scored by API Evangelist on 2026-11-01.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/vergesense"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/vergesense/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/vergesense/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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