BoxFetch integrations

Integrate BoxFetch into agent workflows

Package useful work. Let agents fetch it.BoxFetch gives agents a controlled way to discover, preview, quote, buy, and access packaged work inside human-set limits. It is built for developers, agent builders, workflow teams, and early beta partners who want useful agent actions without hiding the budget, approval, and access boundaries from the human owner.
DevelopersAgent setup previewControl Center preview →

Integration shapes

How teams connect BoxFetch

Ecosystem proof without implying fake official integrations. Manual setup, MCP-style tools, and explicit-media-id boundaries.

01

Website and control center

Use the public website for discovery and the BoxFetch Control Center for agent tokens, budgets, approval thresholds, and activity review.

02

MCP-style tools

Connect a manually configured client to the asset tools for search, preview, quotes, purchases, approvals, content access, feedback, and budget checks.

03

Custom HTTP workflows

Build custom workflow steps around the same product boundaries: preview first, quote before purchase, and unlock content only after a captured purchase.

04

Seller packaging

Turn useful work into reusable boxes with buyer-safe previews, clear scope, pricing in BoxFetch credits, and seller-owned packaging.

05

Media workflows

Media integrations are explicit-id and controlled beta only. There is no MCP media discovery, no MCP media search, no MCP media preview, no MCP media playback, and no MCP media download.

Workflow proof

Example workflows

Real integration shapes with explicit safety boundaries at each step.

Agent buys a box

  1. 1Search assets
  2. 2Preview buyer-safe metadata
  3. 3Quote the box
  4. 4Purchase inside the agent budget

Safety boundary: full content stays locked until the purchase is captured.

Agent waits for human approval above threshold

  1. 1Quote the asset
  2. 2Attempt purchase above the owner threshold
  3. 3Wait while the owner reviews
  4. 4Continue after approval

Safety boundary: the agent cannot bypass the owner threshold.

Agent fetches purchased content

  1. 1Confirm the purchase is captured
  2. 2Call get_asset_content
  3. 3Use the returned package in the workflow

Safety boundary: preview and quote calls never return the full purchased content.

Seller packages a reusable box

  1. 1Define the useful work
  2. 2Write buyer-safe preview copy
  3. 3Set pricing in BoxFetch credits
  4. 4Publish for controlled discovery

Safety boundary: sellers package reusable work without changing payout, wallet, or production-money behavior.

Media workflow with explicit media id and access-controlled human watch

  1. 1Start with a known media id
  2. 2Quote the media id
  3. 3Purchase on the controlled beta rail
  4. 4Send the human to the access-controlled BoxFetch watch surface

Safety boundary: no MCP media discovery, no MCP media playback, and no MCP media download.

Reference

Tool surfaces

Public-facing tool groups for integration planning. Asset surface covers packaged boxes; media surface is controlled beta for explicit media ids only.

Asset tools

search_assets

Find discoverable boxes that are available to the connected agent.

preview_asset

Read buyer-safe preview text and metadata before any purchase.

quote_asset

Request a short-lived quote priced in internal BoxFetch credits.

purchase_asset

Purchase inside the agent limit or pause for the owner threshold.

get_purchase_approval

Read the state of a human approval request when a purchase needs review.

get_asset_content

Fetch purchased content only after the purchase is captured.

submit_usage_feedback

Send structured feedback about a purchased box.

get_agent_budget

Check the remaining agent budget before the next action.

Controlled-beta media tools

boxfetch_media_quote

Quote one explicit media id on the controlled beta rail without exposing provider, stream, token, storage, or wallet internals.

boxfetch_media_purchase

Use the current BoxFetch controlled beta rail for one explicit media id; media purchase and approval behavior follows that rail.

boxfetch_media_access

Read safe access status for one explicit media id while human watch remains access-controlled through BoxFetch.

Boundaries

Current limits

Honest constraints on money, connectors, and media access.

  • internal BoxFetch credits only
  • no production money movement
  • no buyer cash-out
  • no external seller payout
  • no public refund UI
  • no Stripe Connect
  • no Plaid
  • no stablecoin
  • no x402
  • no official connector claim for Claude or ChatGPT
  • no MCP media discovery
  • no MCP media playback
  • no MCP media download
  • no public media discovery

Prepare an integration inquiry

Start with the integration shape, the work agents should fetch, and the controls the human owner needs.

  • Know what they want agents to fetch.
  • Know whether they need boxes, media, approvals, budgets, seller packaging, or custom workflows.
  • Know whether they need public docs, GitHub examples, or a controlled beta walkthrough.
Open developers pagePrepare integration inquiry