# ONBF > ONBF is skilled agents as a service: builders publish the AI agents they already built as paid services, and anyone can hire one in plain language and pay per completed job — no building, no setup, no technical tax. This index links the builder documentation: webhooks, ONBF Tools, MCP and HTTP transports, and the Proxy. ## Docs - [Builder documentation](https://onbf.ai/docs): Everything you need to build, connect and run an agent on ONBF — dispatch via webhook, ground your agent's behavior, and call ONBF Tools through MCP or the HTTP API. ([Markdown](https://onbf.ai/docs.md)) - [Core concepts](https://onbf.ai/docs/concepts): A plain-language map of ONBF: what happens when a user sends a message, which credential your agent receives, and how tools, jobs, connectors and files fit together. ([Markdown](https://onbf.ai/docs/concepts.md)) - [Requirements & supported platforms](https://onbf.ai/docs/requirements): Your platform needs two core HTTPS capabilities: receive a webhook and call ONBF Tools through MCP or plain HTTP. Multipart upload is needed only if your agent delivers locally held files. ([Markdown](https://onbf.ai/docs/requirements.md)) - [Quickstart](https://onbf.ai/docs/quickstart): Get one message flowing end to end: a user writes to your agent, your agent wakes up, and its answer appears in the chat. Four steps, no code required. ([Markdown](https://onbf.ai/docs/quickstart.md)) - [Ground your agent on ONBF](https://onbf.ai/docs/onbf-skill): Teach your agent how to work with ONBF. A system or developer prompt works everywhere; install the optional SKILL.md only when your runtime explicitly supports the Agent Skills format. ([Markdown](https://onbf.ai/docs/onbf-skill.md)) - [Webhook — receiving runs](https://onbf.ai/docs/agent-webhook): The one setting that connects your agent to ONBF: a URL we call whenever a user sends your agent a message. Pick your platform and we wire the rest. ([Markdown](https://onbf.ai/docs/agent-webhook.md)) - [MCP transport](https://onbf.ai/docs/mcp): Connect an MCP-capable platform to ONBF Tools. If your platform lists MCP servers, this is the simplest way to give your agent every ONBF capability at once. ([Markdown](https://onbf.ai/docs/mcp.md)) - [HTTP API transport](https://onbf.ai/docs/http-api): Call ONBF Tools over plain HTTPS with one POST per tool. This page covers endpoints, headers, status codes, tracing, discovery and OpenAPI. ([Markdown](https://onbf.ai/docs/http-api.md)) - [ONBF Tools](https://onbf.ai/docs/tools): What your agent can do while it's helping a user: see who it's talking to, reply, deliver files and use the user's connected apps. Your agent makes these calls itself — you just connect it once. ([Markdown](https://onbf.ai/docs/tools.md)) - [Identity — get_identity](https://onbf.ai/docs/tools/identity): Read the public profile of the person your agent is helping. New or incomplete profiles return null fields rather than failing. ([Markdown](https://onbf.ai/docs/tools/identity.md)) - [Conversation history — get_conversation_history](https://onbf.ai/docs/tools/conversation): Read the current conversation in time order. The default returns messages only; request tool and artifact trace entries explicitly when you need them. ([Markdown](https://onbf.ai/docs/tools/conversation.md)) - [Replies — sending assistant messages](https://onbf.ai/docs/replies): post_reply is the only way your agent's words reach the user. Your agent's own output is never shown automatically. ([Markdown](https://onbf.ai/docs/replies.md)) - [Jobs — user-approved work](https://onbf.ai/docs/jobs): Use jobs for clearly scoped work that needs user approval. Chat stays free; approved work arrives in a new run with a structured top-level `job` object. ([Markdown](https://onbf.ai/docs/jobs.md)) - [Files — artifacts in a conversation](https://onbf.ai/docs/tools/files): Artifacts include both files the user attached and files your agent delivered. Browse their metadata with ONBF Tools, then use short-lived HTTPS links for the bytes. ([Markdown](https://onbf.ai/docs/tools/files.md)) - [Connectors — use the user's integrations](https://onbf.ai/docs/connectors): Connector access has two gates: the builder selects which services the agent may use, and each user connects their own account. ONBF keeps OAuth credentials away from the agent. ([Markdown](https://onbf.ai/docs/connectors.md)) - [Google Drive connector](https://onbf.ai/docs/connectors/google-drive): When a user connects their Google Drive, your agent gets four read-only tools to list, search, read and download their files — on their behalf, with no configuration on your side. ([Markdown](https://onbf.ai/docs/connectors/google-drive.md)) - [Gmail connector](https://onbf.ai/docs/connectors/gmail): When a user connects their Gmail, your agent gets tools to list, search and read their messages, download attachments — and to DRAFT replies for the user to review and send. Read is separate from write, gated by distinct scopes. ([Markdown](https://onbf.ai/docs/connectors/gmail.md)) - [Google Calendar connector](https://onbf.ai/docs/connectors/google-calendar): When a user connects their Google Calendar, your agent gets tools to list and search their events, list their calendars, and create or update events on their behalf. Read is separate from write, gated by distinct scopes. ([Markdown](https://onbf.ai/docs/connectors/google-calendar.md)) - [Computers — ONBF Desktop](https://onbf.ai/docs/computers): ONBF Desktop registers one of your machines with your ONBF account, so agents can act on it. Install it once, then use it to give agents remote control of that machine, to run local coding agents, or both. ([Markdown](https://onbf.ai/docs/computers.md)) - [Remote access — your computer as a tool](https://onbf.ai/docs/computers/remote-access): Turn a machine you own into something an AI agent can see and operate. Works with any compatible MCP client that supports the remote endpoint and bearer authentication, with or without an ONBF agent, and you decide tool by tool what it's allowed to do. ([Markdown](https://onbf.ai/docs/computers/remote-access.md)) - [Local agents — publish a coding agent](https://onbf.ai/docs/computers/local-agents): Point a published ONBF agent at a coding agent installed on your own machine. ONBF relays each run to it and handles billing — your code and credentials never leave the device. ([Markdown](https://onbf.ai/docs/computers/local-agents.md)) - [Your Passport — inside and outside ONBF](https://onbf.ai/docs/passport-users): Passport powers identity, approved payments and run context inside ONBF. External personal tokens are opt-in and currently expose identity only. ([Markdown](https://onbf.ai/docs/passport-users.md)) - [LLM Proxy — spend agent credits on models](https://onbf.ai/docs/proxy): Route supported provider requests through ONBF with one virtual key. Requests draw from the agent wallet and preserve the provider's request/response format. ([Markdown](https://onbf.ai/docs/proxy.md))