TinyFish
for LuumenAI

Web automation, live search, and browser profiles from the terminal

Connect TinyFish and Luumen can search the live web, render pages, and pull content from up to ten URLs at once while you stay in the terminal. It also reads your automation runs, research history, wallet balance, and Browser Context Profiles. Changes — creating a profile, starting a setup session, canceling runs — are previewed and approved first.

The TinyFish toolbox

23 tools: 11 read, 12 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadFetch URLsRender and extract content from 1-10 URLs in one provider-native batch.
  • ReadGet ProfileGet one Browser Context Profile and its saved-domain metadata.
  • ReadGet RunsGet summary records for 1-100 TinyFish automation run IDs in one request.
  • ReadGet WalletGet the TinyFish wallet balance, auto-reload and pending-top-up state, and current Agent and Browser rates.
  • ReadList ProfilesList Browser Context Profiles available to the connected TinyFish account.
  • ReadList Research RunsList saved TinyFish research runs with optional status, query, date, and sort filters, returning one cursor-controlled page.
  • ReadList RunsList automation runs with optional status, goal, date, and sort filters, returning one cursor-controlled page.
  • ReadList UsageList one page of Search, Fetch, or Browser usage history.
  • ReadList Vault ConnectionsList display-safe metadata for password-manager vaults connected to TinyFish.
  • ReadList Vault ItemsList display-safe metadata for items synchronized from password-manager vaults connected to TinyFish.
  • ReadSearch WebSearch live web pages, news, or research papers with domain and time filters, optionally fetching result pages inline, and return exactly one caller-selected zero-based result page.
  • WriteCancel Profile Setup SessionCancel a Browser Context Profile setup session and permanently discard its unsaved cookies and browser storage. Approval by default
  • WriteCancel RunsIdempotently cancel one or up to 100 asynchronous or SSE runs. Approval by default
  • WriteCreate Browser SessionCreate an isolated TinyFish remote browser session and return its CDP connection URL. Approval by default
  • WriteCreate ProfileCreate a reusable Browser Context Profile for cookies and browser storage; this changes persistent account state. Approval by default
  • WriteDelete ProfilePermanently delete a Browser Context Profile and all browser state saved in it. Approval by default
  • WriteDelete Profile DomainPermanently remove saved cookies and browser storage for one domain from a Browser Context Profile. Approval by default
  • WriteSave Profile Setup SessionPersist cookies and browser storage from a completed setup session into a Browser Context Profile, then clean up the temporary session. Approval by default
  • WriteStart Profile Setup SessionStart a billable temporary remote browser session for establishing login state in a Browser Context Profile. Approval by default
  • WriteSync Vault ItemsRefresh display-safe item metadata from all password-manager vaults already connected to TinyFish. Approval by default
  • WriteTerminate Browser SessionIdempotently terminate a remote TinyFish browser session to stop further browser usage charges. Approval by default
  • WriteUpdate ProfileRename a Browser Context Profile or change its default and proxy-country settings. Approval by default
  • WriteUpload Profile StateUpload cookies and local or session storage directly into a Browser Context Profile. Approval by default

One prompt, start to finish

What a governed TinyFish run looks like inside Luumen.

Questions

How does LuumenAI connect to TinyFish?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in TinyFish on its own?

Read actions answer immediately. Anything that writes — cancel profile setup session, cancel runs, create browser session, create profile, and more — is shown as a plan and requires approval by default, including the 7 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to TinyFish — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put TinyFish to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.