VEIR

VEIR is a superconducting power delivery company founded in 2019 and headquartered in Woburn, Massachusetts. It builds low- and medium-voltage high-temperature superconducting (HTS) transmission systems that carry five to ten times more power than conventional conductors at the same voltage level, with roughly 90% less resistive line loss, targeted at AI data center campuses, energy producers, utilities and OEMs. Investors include Microsoft's Climate Innovation Fund, National Grid Partners, Breakthrough Energy Ventures, Congruent Ventures, The Engine Ventures, Galvanize Climate Solutions, Piva Capital, Tyche Partners and VXI Capital. VEIR is a hardware company and publishes no product API or developer program, but it does publish a deliberate agent-facing content layer on veir.com — a markdown twin of every indexed page, a semantic index at /sitemap.md, an RFC 9727 API catalog, OpenID Connect and RFC 9728 OAuth protected-resource discovery documents, and a Content-Signal AI usage preference in robots.txt.

VEIR publishes 1 API on the APIs.io network. Tagged areas include Company, Energy, Electricity, Data Centers, and Infrastructure.

VEIR’s developer surface includes engineering blog, support, authentication, and 12 more developer resources.

21.8/100 emerging ▬ flat Agent 12/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs
CompanyEnergyElectricityData CentersInfrastructureSuperconductorsContent

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 21.8/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 3.0 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 0.0 / 11
Governance 0.3 / 10
Discoverability 6.5 / 9
Regulatory Posture 8.5 / 15
Agent readiness — 12/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities 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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/veir: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

VEIR Markdown Content Endpoint

The single HTTP endpoint VEIR declares in its own RFC 9727 API catalog. It returns veir.com page content as text/markdown for agent consumption. Probed 2026-08-05: it returns HT...

Security Posture 2

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

Veir Authentication

openIdConnect/oauth2 · 2 schemes

SECURITY

Veir Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Veir Scopes

3 scopes · authorizationCode/clientCredentials

3 scopes

SCOPES

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Access & Security 3

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: veir
name: VEIR
description: VEIR is a superconducting power delivery company founded in 2019 and headquartered in Woburn, Massachusetts.
  It builds low- and medium-voltage high-temperature superconducting (HTS) transmission systems that carry five to ten times
  more power than conventional conductors at the same voltage level, with roughly 90% less resistive line loss, targeted at
  AI data center campuses, energy producers, utilities and OEMs. Investors include Microsoft's Climate Innovation Fund, National
  Grid Partners, Breakthrough Energy Ventures, Congruent Ventures, The Engine Ventures, Galvanize Climate Solutions, Piva
  Capital, Tyche Partners and VXI Capital. VEIR is a hardware company and publishes no product API or developer program, but
  it does publish a deliberate agent-facing content layer on veir.com — a markdown twin of every indexed page, a semantic
  index at /sitemap.md, an RFC 9727 API catalog, OpenID Connect and RFC 9728 OAuth protected-resource discovery documents,
  and a Content-Signal AI usage preference in robots.txt.
image: https://images.prismic.io/veir/ad7Kup1ZCF7ETMhn_veir-og-image.png?auto=format,compress&rect=0,0,1200,630&w=2400&h=1260
url: https://raw.githubusercontent.com/api-evangelist/veir/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Company
- Energy
- Electricity
- Data Centers
- Infrastructure
- Superconductors
- Content
apis:
- aid: veir:markdown
  name: VEIR Markdown Content Endpoint
  description: 'The single HTTP endpoint VEIR declares in its own RFC 9727 API catalog. It returns veir.com page content as
    text/markdown for agent consumption. Probed 2026-08-05: it returns HTTP 200 with content-type text/markdown but ignores
    query parameters — /api/markdown, /api/markdown?path=/about and /api/markdown?url=/about all returned the byte-identical
    homepage document. The per-page markdown twins indexed at /sitemap.md (append .md to a page path) are the working surface.
    This is a content endpoint, not a product API; VEIR publishes no OpenAPI describing it.'
  humanURL: https://veir.com/sitemap.md
  baseURL: https://veir.com/api/
  tags:
  - Content
  - Markdown
  - Agents
  properties:
  - type: APICatalog
    url: well-known/veir-api-catalog.json
  - type: Documentation
    url: https://veir.com/sitemap.md
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://veir.com/
- type: Blog
  url: https://veir.com/news
- type: Support
  name: Contact VEIR
  url: https://veir.com/contact-us
- type: PrivacyPolicy
  url: https://veir.com/privacy-policy
- type: TermsOfService
  name: Supplier Terms & Conditions
  url: https://veir.com/suppliertermsandconditions
- type: WellKnown
  url: well-known/veir-well-known.yml
- type: APICatalog
  url: well-known/veir-api-catalog.json
- type: ContentSignal
  name: Content-Signal AI usage preference (robots.txt)
  url: well-known/veir-robots.txt
- type: LLMsTxt
  url: llms/veir-llms.txt
- type: Authentication
  url: authentication/veir-authentication.yml
- type: OpenIDConnect
  url: well-known/veir-openid-configuration.json
- type: OAuthScopes
  url: scopes/veir-scopes.yml
- type: Conventions
  url: conventions/veir-conventions.yml
- type: Conformance
  url: conformance/veir-conformance.yml
- type: DomainSecurity
  url: security/veir-domain-security.yml
x-enrichment:
  date: '2026-08-05'
  status: minimal
  artifacts_added: 12
  pass: local-v1
x-coverage:
  state: none
  reason: not-a-software-company
  detail: VEIR sells superconducting cable hardware, not software — veir.com serves an agent content layer (markdown twins,
    /sitemap.md, an RFC 9727 api-catalog) but the only API it names, https://veir.com/api/markdown, is a content endpoint
    that ignores its parameters, and the OIDC discovery document it publishes advertises authorization, token and JWKS endpoints
    that all return 404.
  evidence:
  - url: https://veir.com/.well-known/api-catalog
    status: 200
  - url: https://veir.com/api/markdown
    status: 200
  - url: https://veir.com/.well-known/openid-configuration
    status: 200
  - url: https://veir.com/oauth/token
    status: 404
  - url: https://veir.com/openapi.json
    status: 404
  - url: https://veir.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-05'