Microsoft Edge
APIs and resources for Microsoft Edge browser development and integration, including the Edge Add-ons API for extension management, DevTools Protocol for browser debugging and automation, Extensions API for building browser extensions, and Web Platform APIs for progressive web app development.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Microsoft Edge the way a machine reads it — 80 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 — Microsoft Edge scores 42.8/100 (developing), with a separate agent-readiness read of 31/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Microsoft Edge'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/microsoft-edge/"
title="Microsoft Edge on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-edge.svg"
alt="Microsoft Edge Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/microsoft-edge/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/microsoft-edge/"
title="Microsoft Edge on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-edge/card.svg"
alt="Microsoft Edge 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 Microsoft Edge
Each block below is one kind of artifact we hold for Microsoft Edge. 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.
Microsoft Edge Extensions API
Build browser extensions for Microsoft Edge using the Chromium-based extensions platform. Supports the WebExtensions API standard for cross-browser compatibility.
Microsoft Edge Web Platform APIs
Modern web APIs and standards supported in Microsoft Edge, including Progressive Web App capabilities, Web Components, and emerging web platform features.
Microsoft Edge Browser API
Browser-level information and management
Microsoft Edge Packages API
Upload and manage extension packages
Microsoft Edge Pages API
Page target management
Microsoft Edge Products API
Manage extension products in the Edge Add-ons store
Microsoft Edge Publishing API
Publish and unpublish extensions
Microsoft Edge Targets API
Discover and manage debuggable browser targets
Scroll within the panel for all 8 ·
Postman Collections 2
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 7
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).
API Collection
OPEN COLLECTIONMicrosoft Edge Add-ons Browser API
OPEN COLLECTIONMicrosoft Edge Add-ons Browser Packages API
OPEN COLLECTIONMicrosoft Edge Add-ons Browser Pages API
OPEN COLLECTIONMicrosoft Edge Add-ons Browser Products API
OPEN COLLECTIONMicrosoft Edge Add-ons Browser Publishing API
OPEN COLLECTIONMicrosoft Edge Add-ons Browser Targets API
OPEN COLLECTIONScroll within the panel for all 7 ·
Arazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Microsoft Edge Find And Close Target
List debuggable targets, branch on whether any exist, and close the first target.
ARAZZOMicrosoft Edge Inspect Browser Environment
Read the browser version and then fetch the full DevTools Protocol schema.
ARAZZOMicrosoft Edge List And Inspect Product
List the developer account's extensions and fetch full details for the first product.
ARAZZOMicrosoft Edge Open And Activate Target
Confirm the DevTools endpoint, open a new tab at a URL, and bring it to the foreground.
ARAZZOMicrosoft Edge Publish Extension Update
Upload a new extension package, wait for validation, then create and track a store submission.
ARAZZOMicrosoft Edge Submit Draft And Track
Create a submission for an already-uploaded draft and poll it until Published or Failed.
ARAZZOMicrosoft Edge Upload Package And Validate
Confirm a product exists, upload a draft package, and poll until the package is validated.
ARAZZOScroll within the panel for all 7 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Microsoft Edge Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Microsoft Edge Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Extension Publishing API
Programmatically publish, update, and manage browser extensions in the Edge Add-ons store via REST API.
Remote Debugging Protocol
Debug and inspect web pages, service workers, and extensions using the Chrome DevTools Protocol over WebSocket.
WebView2 Embedding
Embed Microsoft Edge rendering engine in native desktop applications using the WebView2 SDK.
Progressive Web App Support
Build installable PWAs with offline capability, push notifications, and system integration.
Cross-Browser Extension Compatibility
Build extensions using the Chromium WebExtensions API standard for cross-browser portability.
Browser Automation
Automate browser tasks including page navigation, target management, and performance profiling.
Extension Sideloading
Load and test unpacked extensions locally during development without publishing to the store.
Manifest V3 Support
Build extensions using the latest Manifest V3 specification with service workers and declarative APIs.
Scroll within the panel for all 8 ·
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Microsoft Edge API Rules
SPECTRALMicrosoft Edge API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
PackageUploadResult
JSON SCHEMAProductList
JSON SCHEMAProduct
JSON SCHEMASubmission
JSON SCHEMABrowserVersion
JSON SCHEMAProtocolSchema
JSON SCHEMATarget
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 7
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Addons Api Package Upload Result Structure
JSON STRUCTUREAddons Api Product List Structure
JSON STRUCTUREAddons Api Product Structure
JSON STRUCTUREAddons Api Submission Structure
JSON STRUCTUREDevtools Api Browser Version Structure
JSON STRUCTUREDevtools Api Protocol Schema Structure
JSON STRUCTUREDevtools Api Target Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Addons Api Product Example
EXAMPLEDevtools Api Target Example
EXAMPLEScroll within the panel for all 7 ·
Security Posture 3
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.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automated Extension Deployment
Use the Add-ons API to automate CI/CD pipelines for publishing and updating browser extensions.
Browser Testing and QA
Leverage DevTools Protocol for automated browser testing, performance auditing, and regression detection.
Custom Browser Controls
Embed Edge rendering in desktop applications for custom browser experiences using WebView2.
Enterprise Content Filtering
Build enterprise extensions for content filtering, security policy enforcement, and compliance monitoring.
Web Scraping and Data Extraction
Use DevTools Protocol to programmatically navigate pages and extract structured data.
Accessibility Testing
Automate accessibility audits using DevTools Protocol to inspect DOM, ARIA attributes, and contrast ratios.
Performance Monitoring
Collect real-time performance metrics, network traces, and JavaScript profiling data via DevTools Protocol.
Progressive Web App Distribution
Build and distribute PWAs through the Microsoft Store with native-like installation and system integration.
Scroll within the panel for all 8 ·
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Azure Active Directory
Authenticate to the Edge Add-ons API using Azure AD OAuth 2.0 client credentials flow.
Microsoft Partner Center
Manage extension listings, submissions, and analytics through the Partner Center dashboard.
Visual Studio Code
Debug Edge browser content directly from VS Code using the Edge DevTools extension.
Selenium WebDriver
Automate Microsoft Edge browser for testing using Selenium with the Edge WebDriver.
Playwright
Cross-browser automation framework with first-class support for Microsoft Edge testing.
Puppeteer
Control headless Microsoft Edge instances programmatically using the Puppeteer Node.js library.
GitHub Actions
Automate extension publishing and browser testing in CI/CD workflows using GitHub Actions.
Windows App SDK
Integrate WebView2 into Windows desktop applications built with WinUI 3 and the Windows App SDK.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for Microsoft Edge — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 4
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 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/microsoft-edge · machine-readable index on apis.io
This is an independent, third-party profile of Microsoft Edge, 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.