Fangst

Input, files, and approvals from people

Give AI agents APIs for getting input, files, and approvals from people.

An agent with a Fangst API token and HTTP access can create the request itself. Fangst returns a hosted URL. The agent shares that URL through a channel available to it, then polls for the response or continues when your application receives submission.completed.

Set up the agent Read the API guide

Give the agent three things.

Add these resources and credentials to the agent's tools or instructions. No Fangst-specific agent protocol is required; the product surface is HTTP.

Discovery
https://fang.st/llms.txt links the human and machine-readable resources.
API contract
https://fang.st/api/ explains the loop; OpenAPI 3.1 lists the implemented v1 operations.
Authorization
A Fangst base URL and API token, stored as secrets and sent as Authorization: Bearer ….

The agent creates, shares and reads the request.

Fangst does not choose a recipient or send the message. The agent or your software must have its own email, chat, SMS or other channel for giving the hosted URL to the right person.

  1. Notice missing input.The agent identifies fields or files only a person can provide.
  2. Create the request.It calls POST /v1/requests with its Bearer token and the required field schema.
  3. Share the hosted URL.It reads request.hosted_url from the response and gives it to the person through an available channel.
  4. Wait for the person.The person fills in the hosted page and uploads the requested files without a Fangst account.
  5. Read the result.The agent polls GET /v1/requests/:id/submissions, or the application handles the signed submission.completed webhook.

Example: a claim agent needs damage photos.

The agent has the claim id but cannot finish its work without a description and photos from the customer. It creates a request with that claim id as metadata and asks for those fields.

Agent hasclaim_id: clm_92831
Person providesDescription, photos and date
Agent receivesStored fields, attachment metadata and the same claim id

Fangst returns what the person submitted. The agent or application decides whether the claim can continue.

Use the same loop whenever an agent needs something from a person.

Customer onboarding

Request company details, identity documents or signed files tied to the customer id.

Claims and support

Request photos, receipts, logs or a written explanation tied to the claim or ticket.

Project intake

Request a detailed brief, reference files and dates before planning can continue.

Approvals

Ask a person to approve, reject or choose before the agent continues.

Let the agent ask. Let the person answer.

Fangst hosts the request and gives the stored response back to the authorized system.

Contact