Envisics
Envisics is a British deep-technology company headquartered in Milton Keynes, United Kingdom, that pioneers dynamic holography for automotive augmented-reality head-up displays (AR HUD). The work began with Dr Jamieson Christmas' PhD at Cambridge University in 2004, continued through Two Trees Photonics (founded 2010, acquired by DAQRI in 2015) which built the world's first laser holographic HUD for Jaguar Land Rover, and was spun out as the independent company Envisics on 1 January 2018. Its Dynamic Holography Platform and next-generation Holographic Waveguide Technology combine proprietary algorithms with simpler, fewer and more robust optics to deliver multi-plane AR imagery at under 10% of the optical power of conventional systems; first-generation technology shipped in over 150,000 Jaguar and Land Rover vehicles and second-generation technology was slated for the Cadillac LYRIQ-V and 2026 Cadillac VISTIQ. Investors included Hyundai Mobis, General Motors Ventures, Stellantis, InMotion Ventures (Jaguar Land Rover) and Tarsadia Investments. Envisics is an automotive hardware and optics supplier rather than a software vendor: it publishes no commercial or developer-facing product API, no developer portal, and no SDKs. The only machine-readable interface it exposes is the WordPress REST content API behind its corporate website at envisics.com, captured here for discovery purposes and anonymously readable but read-only. Envisics Ltd. entered administration on 22 April 2026 under the Insolvency Act 1986, with Geoff Rowley and Simon Carvill-Biggs of FRP Advisory Trading Limited appointed as Joint Administrators.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Envisics the way a machine reads it — 21 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Envisics scores 32.2/100 (thin), with a separate agent-readiness read of 51/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from Envisics's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/envisics/"
title="Envisics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/envisics.svg"
alt="Envisics Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/envisics/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/envisics/"
title="Envisics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/envisics/card.svg"
alt="Envisics Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Envisics
Each block below is one kind of artifact we hold for Envisics. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Envisics Posts API
Public, unauthenticated read access to the Envisics newsroom archive — press releases, news items, tech-shorts and did-you-know posts — via the WordPress core REST API. Verified...
Envisics Pages API
Public, unauthenticated read access to the static pages of envisics.com — Products, Technology, Company, Newsroom, Multi Media, Careers, Contact, Terms of Use, Supplier Terms & ...
Envisics Media API
Public, unauthenticated read access to the media library behind envisics.com — AR HUD product imagery, holographic waveguide renders, press photography and brand assets with the...
Envisics Taxonomy API
Public, unauthenticated read access to the classification vocabularies behind envisics.com: the newsroom categories that separate news, press, tech-shorts, white-papers and did-...
Envisics Search API
Public, unauthenticated cross-content search over envisics.com — posts and pages — returning lightweight id / title / url / type / subtype records. Verified live at 62 searchabl...
Envisics Discovery API
Public, unauthenticated discovery metadata for envisics.com — the registered content types and taxonomies, the publication statuses, and the public author records. This is the s...
Envisics oEmbed API
Public oEmbed 1.0 provider endpoint for envisics.com URLs, returning embeddable rich metadata — title, author, dimensions and iframe HTML — for any post or page on the site.
Envisics SEO Metadata API
Public Yoast SEO head endpoint returning the rendered head metadata and its parsed JSON-LD schema.org graph for any envisics.com URL — a structured-data view of every page witho...
Scroll within the panel for all 8 ·
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Envisics Discovery API
OPEN COLLECTIONEnvisics Media API
OPEN COLLECTIONEnvisics oEmbed API
OPEN COLLECTIONEnvisics Pages API
OPEN COLLECTIONEnvisics Posts API
OPEN COLLECTIONEnvisics Search API
OPEN COLLECTIONEnvisics SEO Metadata API
OPEN COLLECTIONEnvisics Taxonomy API
OPEN COLLECTIONScroll within the panel for all 8 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Envisics Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Envisics — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/envisics · machine-readable index on apis.io
This is an independent, third-party profile of Envisics, 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.