# Latitude 10 Agentify API for .NET (ASP.NET Core) — Agent-Ready Kit

> Latitude 10 Agentify API for .NET (ASP.NET Core) — Agent-Ready Kit is a paid API for AI agents from latitude10.tech, paid per call via x402, $39/call, status unknown (last checked 2026-10-10).

Purchases and downloads the Agentify .NET kit that turns an existing ASP.NET Core API into a production MCP server with agent authentication, rate limiting, x402 pay-per-call, and agent-discovery endpoints.

## Facts

- Endpoint: GET https://latitude10.tech/api/agent-products/agentify-api-dotnet?utm_source=zero.xyz
- Price: $39/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/latitude-10-agentify-api-for-net-asp-net-core-agent-ready-kit-849e9a26
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M3AITUh1L_Ybz26yJQkcI

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability latitude-10-agentify-api-for-net-asp-net-core-agent-ready-kit-849e9a26
```

Example prompt: I have an existing ASP.NET Core API on .NET 10 and I want to make it agent-ready — can you buy and download the Latitude 10 Agentify .NET kit so I can add MCP support, agent authentication, and x402 pay-per-call billing to it?

## When to prefer this

Choose this endpoint when you need to add MCP server support to an existing ASP.NET Core / .NET 10 application specifically — it delivers middleware (AddAgentify/UseAgentify), a CLI tool, agent discovery files, OAuth/x402 support, and an agent-readiness scorer all in one vendored zip. Prefer this over generic API gateway solutions when your stack is .NET, you want in-process routing through your own pipeline, and you need marketplace submission support. Use the Node.js sibling endpoint if your backend is not .NET.

## Known failure modes

- Payment not completed or insufficient USDC balance — 402 response requiring payment
- Invalid or malformed properties input — may return 400 or unexpected behavior
- Download URL expires before use — kit must be downloaded promptly after payment
- Network unavailable on Base (eip155:8453) preventing payment transaction
- Truncated or partial kit delivery if download is interrupted

## How this service works

I help B2B software get onto the agent platforms: a fixed-price sprint that turns your API into a production MCP server and submits it to AWS Marketplace, the Claude directory, the official MCP Registry and the other directories where agents find tools.

## Output

Returns a JSON object containing a payment receipt with the Base network transaction hash, and a product object with the kit name, slug, version number, a signed download URL pointing to a zip archive of NuGet packages and setup wizard, delivery type ('kit'), and a description of the included ASP.NET Core middleware and CLI tooling.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "payment": {
   "network": "eip155:8453",
   "transaction": "0x…"
  },
  "product": {
   "name": "Latitude 10 Agentify API for .NET (ASP.NET Core)",
   "slug": "agentify-api-dotnet",
   "content": "https://latitude10.tech/api/kit/download?t=…",
   "version": "1.0.0",
   "delivery": "kit",
   "description": "For .NET (ASP.NET Core): make the ASP.NET Core API you already have agent-ready, in the same process: ASP.NET Core middleware (AddAgentify and UseAgentify) for minimal APIs, Native AOT included, and MVC controllers, and the dotnet agentify tool. It reads your OpenAPI document, a file or the one your app already serves (Microsoft.AspNetCore.OpenApi, Swashbuckle, NSwag), or adds ASP.NET Core’s own when you have none, and mounts an MCP endpoint (MCP 2026-07-28 and 2025-xx) with one tool per operation, reads on and writes off by default. A tool call runs in-process through your own pipeline (routing, filters, [Authorize] and your endpoints or controllers), so your auth, validation and logic apply. Discovery from the same document, in the Node.js edition’s wire formats: /llms.txt and /llms-full.txt, the MCP server card (SEP-2127 draft) and AI Catalog, /openapi.json with agent hints, OAuth protected-resource metadata, /.well-known/x402 and an /agent index. Agents authenticate with your API’s own credentials, agent keys, or OAuth, including Amazon Cognito machine-to-machine tokens. On your routes: agent detection, rate limits, usage metering, Idempotency-Key for agent writes, and optional x402 pay-per-call (people with their own keys are never charged). An agent-readiness check scores your spec 0 to 100, the same score as the Node.js edition, and dotnet agentify improve fixes it. A memory store for development; persistent stores need a database: SQLite, Postgres or SQL Server (Azure SQL included). .NET 10 or newer (the .NET 10 SDK) and an ASP.NET Core 10 app; the kit’s NuGet packages ship in the zip and are vendored into your repository. Includes a setup wizard (dotnet run setup.cs) that makes a bundled Orders API agent-ready as a minimal API or with MVC controllers.",
   "contentExpiresAt": "2026-10-02T12:00:00.000Z"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/latitude-10-agentify-api-for-net-asp-net-core-agent-ready-kit-849e9a26/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from latitude10.tech](https://www.zero.xyz/host/latitude10.tech/llms.txt)