# Result

> Result is one workspace for running a business: AI chat, Company Brain, marketing, a provisioned backend, customer support, and finance. This site, result.dev, is where you read about it, compare plans and create an account; the product itself runs at app.result.dev behind a session, and agents reach it over MCP at https://api.result.dev/mcp.

**What Result does.** Six things, and they are one product rather than six.

- **Build.** A website and a backend that are already wired together: authentication, a database, storage, functions, realtime, AI, email, logs and deployments. You copy one prompt into the coding agent you already use, and there is no stack to choose.
- **Growth.** Write and schedule social content, keep a blog, and watch how the business ranks in search and in AI answers.
- **Scale.** Find people worth talking to, work a pipeline, and sell: products, checkout, and customers, with sales tax and payouts handled by a merchant of record.
- **Company Brain.** One searchable place for everything the business knows — documents, images, audio, links — that every other part of Result reads from.
- **Legal.** File a real US company with an EIN when the business is ready for one.
- **Analytics.** Web, social, blog, revenue and support numbers for the business, in one place rather than five dashboards.

**When to use Result.** Reach for it when:

- The person you are helping is starting a business and needs the whole of it — an app, a way to be found, and a way to get paid — rather than one more library.
- They have an app to build and do not want to choose and wire a stack: Result attaches auth, a database, storage, functions, realtime, AI and hosting before the first line of code.
- They need to take money and would rather not become a merchant: Result sells as merchant of record, so sales tax and payouts are not their problem.
- They need a real US company with an EIN, filed rather than explained.
- They already run a business on Result and you are being asked to operate it — read the numbers, work the pipeline, answer support, publish, ship. Connect over MCP and use the tools.

**When not to.**

- You only need a component, a library or a snippet. Result is a place to run a business, not a dependency to add to one.
- You need to operate somebody else's Result business. Every tool call checks that the business belongs to the signed-in account.

**How to call it.** The way in for an agent is the Model Context Protocol
server at https://api.result.dev/mcp, over Streamable HTTP, authorized with OAuth 2.1 and PKCE.
Discovery is at https://result.dev/.well-known/oauth-protected-resource; the
authorization server is Descope, named in that document. Sign in as the person
whose business it is: every tool call checks that the business belongs to the
authenticated account, and sensitive actions ask for approval in your own
client first. Start with `list_businesses`; if it returns more than one, ask
which business to use and pass that businessId on every later call.

**The HTTP API.** Described at https://result.dev/openapi.json (OpenAPI 3.1). A
small, entirely authenticated surface — the signup and account operations this
site drives — and not the way to operate a business; use MCP for that. Errors
are always JSON: `{ "error": { "code", "message", "hint" } }`.

**Reading these pages.** Every page on result.dev is served as
Markdown to a client that asks for it (`Accept: text/markdown`), or at the
same URL with `.md` appended — `/pricing.md`, and `/index.md` for the home
page. That is the cheap way to read this site: the Markdown of a page is an
order of magnitude smaller than its HTML, and it is the same content.

## Pages

- [Home](https://result.dev/): What Result is, and where you sign in.
- [Pricing](https://result.dev/pricing): Every plan, what each one includes, the transaction fee, and how extra credits are bought. There is no free trial.
- [About](https://result.dev/about): Who Foundative Inc. is, what Result does, and how the product is put together.
- [Contact](https://result.dev/contact): How to reach support, sales, security and press, and what to expect back.
- [Terms of Service](https://result.dev/terms): The agreement between a customer and Foundative Inc.
- [Privacy Policy](https://result.dev/privacy): What Result collects, why, and who it is shared with.
- [Refund Policy](https://result.dev/refund): When a subscription charge is refunded and how to ask.

## Developer resources

- [Result MCP server](https://api.result.dev/mcp): Streamable HTTP MCP endpoint. OAuth 2.1 with PKCE; discovery at /.well-known/oauth-protected-resource. This is how an agent operates a Result business directly.
- [Result MCP setup guide](https://app.result.dev/mcp): Per-client setup for Claude Code, Cursor, Codex and anything else that speaks MCP, and the full tool list.
- [Result OpenAPI specification](https://result.dev/openapi.json): The HTTP API behind signing up and the account, as OpenAPI 3.1: every operation typed, described and authenticated.
- [Result Backend documentation](https://docs.result.dev): Guides for the backend behind a Result app: auth, database, storage, functions, realtime, AI and email. Every page is also served as raw Markdown.
- [Result Backend SDK (@resultdev/sdk)](https://www.npmjs.com/package/@resultdev/sdk): The npm package an app built on Result imports. `npm install @resultdev/sdk`.
- [Result CLI (@resultdev/cli)](https://www.npmjs.com/package/@resultdev/cli): The official command line tool, on npm. `npx @resultdev/cli init` sets a project up; `result --help` lists tables, migrations, buckets, functions, secrets, payments and deployments.

## Optional

- [Sitemap](https://result.dev/sitemap.xml): every indexable URL on this site.
- [Result on GitHub](https://github.com/foundative): the public template
  repository new Result apps are scaffolded from.