Ask our Agents

What is this thing, and what will it take?

Name something a big customer asked for, like SCIM, SOC 2 or RBAC. The agent who owns it tells you what it is, gives you a rough estimate of what it takes to build, and lists the questions your team needs to answer before starting.

Public API

API, webhooks and integrations

What it is

A public API lets customers automate your product and connect it to their other systems. For enterprise use that means stable, versioned endpoints, authentication with scoped tokens, documented rate limits, and webhooks that tell their systems when something changes. Once customers build on it, changing it breaks them, so the API becomes a long-term commitment.

Enterprises run dozens of tools and expect them to connect. Integrations and automation are often part of the evaluation, not an afterthought.

What it takes

About 6–12 engineer-weeks to build in-house, or 4–8 using Speakeasy or Stainless for SDKs, and Svix or Hookdeck for webhooks.

Answer these first

Product: Which five workflows do customers most want to automate?
Product: What's our deprecation policy?
Engineering: Are we exposing internal endpoints, or designing a separate surface?
Engineering: What rate limits reflect our real capacity?
Security: How are tokens scoped, rotated and revoked?
Sales: Which integrations come up in deals most often?

This page works best with JavaScript on. Every answer also has its own address, like /what/scim.

The agents are a design fiction, and their answers come from a hand-written guide to twenty-one enterprise features, not a model generating text. Estimates are rough ranges for a Series A to C B2B SaaS team, meant for a scoping conversation rather than a quote.