---
schema_version: "newruntime-agent-readable-v0.1"
type: "trend_pattern"
slug: "agent-ready-software-exposes-capabilities"
title: "Agent-ready software exposes capabilities"
description: "Software is becoming easier for agents to use when it exposes explicit operations, schemas, temporary identity, and isolated execution instead of only adding a chat widget."
thesis: "The agent-ready product boundary is a small set of observable, permissioned capabilities that external agents can compose safely."
status: "published"
confidence: "high"
first_seen: "2026-06-23"
last_verified: "2026-07-16"
supporting_signals: ["tg-2581","tg-2711","tg-2514","tg-2660","tg-2686","tg-2530"]
related_posts: ["agent-api-design","hilos-development-control-plane"]
counter_evidence: ["Human-oriented applications still need visual workflows, explanation, recovery, and controls that a narrow agent API does not provide.","Exposing more capabilities can increase attack surface and operational complexity when identity, authorization, and audit are weak."]
revision_trigger: "Revise the thesis if embedded assistant interfaces consistently outperform explicit capability APIs on interoperability, reliability, permission control, and integration cost."
topics: ["agent-ready","api-design","agent-infrastructure"]
source_urls: ["https://blog.cloudflare.com/code-mode-mcp","https://x.com/EnoReyes/highlights","https://blog.cloudflare.com/temporary-accounts","https://trycase.dev/docs","https://github.com/tencentcloud/CubeSandbox"]
routes: {"html":"https://newruntime.com/patterns/agent-ready-software-exposes-capabilities/","markdown":"https://newruntime.com/patterns/agent-ready-software-exposes-capabilities.md","json":"https://newruntime.com/patterns/agent-ready-software-exposes-capabilities.json"}
source_format: "markdown"
---

# Agent-ready software exposes capabilities

## What is changing

An agent cannot reliably use a product because the product has a chatbot. It
needs explicit operations, typed inputs, bounded outputs, identity, permissions,
and state that can be inspected after the action. Cloudflare's code-mode MCP
work, temporary accounts, disposable execution environments, and resource
discovery all move those requirements into product infrastructure.

## Supporting evidence

- Code-mode MCP reduces a large tool surface to compact programmable operations.
- Stable REST resources can be easier for an agent to inspect than a client SDK
  that hides network behavior and state.
- Temporary accounts and disposable sandboxes give non-human workers a scoped
  identity and execution boundary.
- Agentic Resource Discovery treats available capabilities as searchable,
  machine-readable inventory.

## Operational consequence

An agent-ready service should publish a capability map, schemas, permission
requirements, idempotency rules, error states, audit identifiers, and a safe
test environment. The public website can then remain the human explanation
while agents use a smaller, stricter contract.