Developers

Build for agents on BoxFetch

Agents can discover and inspect boxes, then preview and buy them — but access stays controlled by the user. Purchases happen through wallet rules and the owner’s approval settings, so an agent fetches the packaged work it needs without spending beyond what its owner allows. Developer setup is early access.
Purchases are wallet-backed and powered by credits — an in-product unit, not cash, with no buyer cash-out. BoxFetch is not an official Claude or ChatGPT connector; setup is manual, using MCP-style or custom HTTP configuration in your own client.
Agent setup previewBrowse marketplaceIntegrations →

What agents can do

Agent capabilities — bounded and honest

Discovery, preview, quote, purchase, and content access inside human-set controls.

01

Discover and preview boxes

Agents search discoverable listings, read buyer-safe previews, and take quotes — never full content before purchase.

02

Buy inside human limits

Purchases capture inside the agent spending limit, or pause for owner approval above the threshold.

03

Unlock after capture

Full content returns only after a captured purchase. Preview never exposes the full package.

04

Explicit media ids only

A narrow MCP media beta supports quote, purchase, and access status for explicit media ids — not discovery, playback, or download through MCP.

Human control

What remains human-controlled

Spending limits, approval thresholds, revocable tokens, and preview-before-purchase.

  • 01Agents use scoped tokens; one token, one agent.
  • 02Owners set spending limits and approval thresholds.
  • 03Larger purchases pause for owner approval before any capture.
  • 04Tokens are revocable at any time from the Control Center.
  • 05Preview comes before purchase. Preview never exposes full content.
  • 06Full content unlock requires a captured purchase.

Get started

Setup entry points

Start here. BoxFetch agent setup is owned by these pages — no need to leave the BoxFetch route family.

Join first 50

First-50 launch access is coming soon. Browse the marketplace and read setup guides during public preview.

Agent setup preview

Read how agent setup will work: control center, scoped tokens, and manual client configuration.

/agent-setup

Browse boxes

See the boxes agents discover through search in the BoxFetch marketplace.

/marketplace

Public launch access

Review the public launch controls, approval rails, and current access limits.

/trust-safety

Reference

Tool reference

MCP-style tools available to a connected agent. Configure them manually through your client’s MCP or custom HTTP setup.

Asset tools

search_assets

List discoverable boxes routed by Trust Works.

preview_asset

Read buyer-safe preview text and metadata. Never returns full content.

quote_asset

Take a short-lived price quote in wallet credits.

purchase_asset

Capture inside the agent spending limit, or open an approval request above the threshold.

get_purchase_approval

Poll the status of an approval request. Content stays locked while pending.

get_asset_content

Return full content only after a captured purchase.

submit_usage_feedback

Post structured feedback for an asset the agent purchased.

get_agent_budget

Read remaining session and daily spend headroom for this agent.

Media for agents — controlled MCP beta, narrow and explicit-id only

Media is a separate, tighter rail on top of the asset surface. A narrow MCP media beta is live: agents can quote, purchase, and read access status for explicit media ids only — never discover, search, preview, stream, or download media through MCP. Human playback stays access-controlled through the BoxFetch watch page.

  • Live MCP-style agent tools cover asset listings (search_assets, preview_asset, quote_asset, purchase_asset, get_purchase_approval, get_asset_content, submit_usage_feedback, get_agent_budget) plus the controlled MCP media tools described below.
  • MCP media tools boxfetch_media_quote, boxfetch_media_purchase, and boxfetch_media_access are live in controlled beta for explicit media ids only — no MCP media discovery, search, or preview.
  • MCP media purchase uses internal BoxFetch credits only through the existing paid-library purchase service; no production money, no external payout, no buyer cash-out is reachable through an agent.
  • An external MCP media purchase that requires human approval creates a media-specific approval request — no settlement and no entitlement at request time. On owner approval, the media approval rail re-reads server-side media state and settles through the existing internal-credit paid-media purchase path; the media entitlement is issued only after successful settlement. Declined, expired, stale, price-changed, or insufficient-credit approvals fail closed without settling.
  • MCP media access returns safe entitlement/watch status and the app watch path only; human playback stays access-controlled through the BoxFetch watch page.
  • No raw playback stream, Cloudflare signed token, iframe src, provider video id, R2 key, download URL, or provider secret is exposed to agents under any surface; MCP does not stream or download media.

Live MCP media tools (explicit media ids only)

These tools accept one explicit mediaAssetId per call. They do not enable MCP media discovery, search, preview, playback, or download, and they never return tokens, iframe src, raw provider ids, R2 keys, streams, or download URLs.

boxfetch_media_quote

Return a safe quote for one explicit media id — eligibility, price in internal BoxFetch credits, library entitlement hint, and the app watch path if already entitled. Never returns playback tokens, iframe src, provider uid, R2 keys, download URLs, or production-money data.

boxfetch_media_purchase

Purchase access to one explicit eligible media id through internal BoxFetch credits only. When external MCP approval is required, the agent creates a media-specific approval request — no settlement and no entitlement at request time. On owner approval, the media approval rail re-reads server-side media state and settles through the existing internal-credit paid-media purchase path; the media entitlement is issued only after successful settlement. Never returns playback or provider data; explicit media ids only.

boxfetch_media_access

Return safe entitlement and watch status for one explicit media id — watchState, accessType, and the app watch path only. Does not issue or expose Cloudflare playback tokens, iframe src, provider uid, R2 keys, bytes, streams, or download URLs.

Current limits

BoxFetch exposes MCP-style rails, not an official vendor listing. No token, iframe src, provider id, R2 key, or download URL is ever returned to an agent. The current limits are honest and narrow:

  • internal BoxFetch credits only
  • no production money movement
  • no buyer cash-out
  • no external payout rail live
  • no MCP media playback
  • no MCP media download

Connector honesty

BoxFetch is not an official Claude connector. BoxFetch is not an official ChatGPT connector. BoxFetch is not listed in any official connector marketplace. Setup is manual, using MCP-style or custom HTTP configuration in your own client.