Conto Monthly Update

In May, we refreshed the Conto brand, launched Enchant in beta, met with the agentic-payments community at Stripe Sessions, and shipped product improvements that customers and developers can use directly.

A refreshed Conto brand

Conto's branding received an overhaul across the public site and product, including a new visual system and modernized logo.

Enchant beta

We launched Enchant in beta, a consumer product built on Conto's spend management platform.

Enchant provides a simpler way to use APIs and AI models through micropayments. People can pay for services in small increments through agentic-payment protocols instead of setting up wallets, agents, and individual provider subscriptions themselves. It is also a public example of the same payment, policy, and approval infrastructure available through Conto.

Stripe Sessions and the agentic-payments community

We hosted a happy hour during Stripe Sessions for founders and operators building in agentic payments and commerce. The conversations covered where agent-driven purchasing is working today and what the ecosystem still needs. Read the event recap.

Clearer trust and policy decisions

Counterparty views now explain the evidence behind a trust score, the signals that raise or lower it, and the next action an operator can take. Policy templates also make it faster to start from a common spending pattern and adapt it to your organization.

Stronger agent identity and ownership

Agent identity fields now appear consistently across the dashboard and APIs. Teams can assign a responsible organization member, keep a durable external reference, label the agent's purpose and environment, and use those fields to search or target policies.

These references make it easier to match a Conto agent to the corresponding runtime in your own system and to understand who should act when a payment needs attention.

More practical wallet and payment operations

Wallet views now present network, custody mode, balance, status, and linked-agent controls in a consistent format. Payment responses preserve the references and lifecycle states needed to check an uncertain result before retrying, including transaction and receipt information when settlement has started.

Conto Pay also gained clearer request links, activity and approval states, and receipt-oriented workflows for teams that prefer a hosted payment experience.

Better billing guidance

Billing views now show current usage, projected overage, and whether an alert still needs action. When a plan limit blocks setup, the response includes the relevant usage and limit so an operator can decide whether to remove an unused resource or change plans.

Faster developer onboarding

The public Build hub brings the SDK, MCP server, CLI, OpenAPI reference, llms.txt, and agent skills together. Machine-readable discovery starts at /.well-known/agent.json, and the SDK setup response gives an integration the agent, wallet, granted scopes, limits, and supported endpoints it needs to begin safely.

We also expanded the guides for custody choices, external approvals, payment testing, and choosing between organization API keys and agent SDK keys.

The common thread is straightforward: expose the information a customer needs to understand a decision, take the next action, reconcile a payment, or complete an integration.