Microsoft .NET
Microsoft .NET is a free, cross-platform, open source developer platform for building many different types of applications. The .NET APIs and developer tools provide programmatic access to .NET runtime services, NuGet package management, project templates, and build tooling across web, mobile, desktop, games, IoT, cloud, and microservices workloads.
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 .NET the way a machine reads it — 34 machine-readable artifacts across 9 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 .NET scores 52.2/100 (developing), with a separate agent-readiness read of 48/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.
How we profile Microsoft .NET
Each block below is one kind of artifact we hold for Microsoft .NET. 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 9
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 .NET API Browser
Comprehensive reference for .NET APIs across all packages, namespaces, and types in the .NET ecosystem including .NET 9, .NET Standard, and .NET Framework.
NuGet Server API
RESTful API for interacting with nuget.org and private NuGet feeds, supporting package search, download, push, delete, and metadata queries for .NET package management.
.NET CLI
Cross-platform command-line interface for developing, building, running, and publishing .NET applications. Provides commands for project creation, package management, testing, a...
ASP.NET Core Web API
Framework for building HTTP-based RESTful APIs and web services with ASP.NET Core, including controllers, minimal APIs, routing, model binding, authentication, and OpenAPI integ...
.NET Aspire
Cloud-ready stack for building observable, production-ready distributed applications in .NET with built-in service discovery, health checks, telemetry, and configuration managem...
Microsoft .NET PackageContent API
The PackageContent API from Microsoft .NET — 3 operation(s) for packagecontent.
Microsoft .NET Registration API
The Registration API from Microsoft .NET — 2 operation(s) for registration.
Microsoft .NET Search API
The Search API from Microsoft .NET — 1 operation(s) for search.
Microsoft .NET ServiceIndex API
The ServiceIndex API from Microsoft .NET — 1 operation(s) for serviceindex.
Scroll within the panel for all 9 ·
Open Collections 1
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).
NuGet Server API (V3)
OPEN COLLECTIONPricing 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.
Microsoft Net 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 Net Finops
FINOPSFeatures 6
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.
Cross-Platform Development
Build and run .NET applications on Windows, macOS, and Linux with full platform support.
High Performance Runtime
.NET runtime with JIT compilation, garbage collection, and ahead-of-time compilation for optimal performance.
NuGet Package Ecosystem
Access over 350,000 packages through the NuGet package manager for rapid development.
Minimal APIs
Build lightweight HTTP APIs with minimal code using the minimal API pattern in ASP.NET Core.
Cloud Native Support
Built-in support for containers, Kubernetes, microservices, and cloud deployment through .NET Aspire.
Hot Reload
Apply code changes to running applications without restarting for faster development cycles.
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 5
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.
Enterprise Web Applications
Build scalable enterprise web applications using ASP.NET Core with authentication, authorization, and data access.
Microservices Architecture
Design and deploy microservices using .NET with gRPC, message queues, and service discovery.
Cloud-Native Applications
Develop cloud-native applications with .NET Aspire, containers, and Azure integration.
RESTful API Development
Create production-ready REST APIs with OpenAPI documentation, versioning, and rate limiting.
Desktop Applications
Build Windows desktop applications using WPF, WinForms, or .NET MAUI for cross-platform desktop.
Integrations 6
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
Deep integration with Microsoft Azure cloud services including App Service, Functions, and Container Apps.
Visual Studio
Full IDE support with IntelliSense, debugging, profiling, and project templates in Visual Studio.
VS Code
Lightweight development with the C# Dev Kit extension for Visual Studio Code.
GitHub Actions
CI/CD pipeline integration with GitHub Actions for .NET build, test, and deploy workflows.
Docker
Container support with official .NET Docker images and multi-stage build templates.
Entity Framework Core
Object-relational mapping for database access with support for SQL Server, PostgreSQL, SQLite, and more.
Resources
Every other property we hold for Microsoft .NET — 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 2
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
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/microsoft-net · machine-readable index on apis.io