Skip to content
CloudSitus

Capability · ETL & search

Ingest, index and search, without a vector DB.

Turn URLs, HTML and text into a searchable vector store, and run live web and deep-research search — a stateless white-label of Twin Browser, billed per use.

Get startedRead the docs

POST /v1/etl · /v1/etl/query · /v1/search

What you get

Built for regulated workloads

ETL and search are a curated, stateless proxy over Twin Browser’s browser-execution API. POST sources to /v1/etl and the upstream extracts, transforms, chunks, embeds and stores them; query them back with /v1/etl/query — no vector database to run. /v1/search adds live web search, and depth:"deep" runs an async research pass you poll at /v1/jobs/{token}. CloudSitus holds no state: the vector store, collections and jobs all live upstream, isolated per customer and billed exactly at the upstream’s rate.

01 · Pipeline

Extract → embed → store

One POST to /v1/etl runs a browser-grade extract, transform, chunk, embed and store over your urls, html or text. Nothing to host — the pipeline and vector store live upstream; you get back a collection you can query.

02 · Retrieval

Semantic query

/v1/etl/query returns the best-matching chunks from your collection with scores — a RAG index without standing up or scaling a vector DB yourself.

03 · Search

Web + deep research

/v1/search returns live web results synchronously; depth:"deep" kicks off an asynchronous research run that you poll at /v1/jobs/{token} until it settles.

04 · Isolation

Per-customer namespace

Every customer’s content is namespaced to its own collection, derived server-side from your API key (never the request body) — a query can only ever reach your own rows. Async jobs return a customer-bound token, not a raw upstream id.

05 · Billing

Billed per use

Each call is billed on the credits it reports, at 1 USD = 1000 credits. Async jobs settle once, on the first terminal poll.

06 · PHI

General traffic only

Twin Browser is not a PHI-eligible host, so an X-PHI:true request returns phi_blocked. ETL and search are general-traffic only.

Availability & pricing

Where it runs, what it costs

Every route is pinned to a region, PHI stays on resident hosts, and the PHI gate is enforced per call. Prices mirror the live /v1/pricing rate card.

RegionProviderModelTierPrice
AllTwin BrowserETL ingest · /v1/etlGeneralPer use
AllTwin BrowserETL query · /v1/etl/queryGeneralPer use
AllTwin BrowserWeb search · /v1/searchGeneralPer use
AllTwin BrowserDeep research · /v1/search (async)GeneralPer use
Any—ETL / search (PHI)No routephi_blocked

Billed per use — the credits each call reports, at 1 USD = 1000 credits. General traffic only.

Try it

A real call, end to end

Ingest a few sources, then query them semantically — no vector DB to run. Everything is scoped to your own collection.

Statelessness & isolation

  • CloudSitus is a stateless proxy — the vector store, collections and job state all live in Twin Browser, not here. Nothing about your content is persisted by the gateway.
  • Every customer shares one upstream tenant, isolated by a per-customer collection namespace derived from your API key (never the request body), so a query can only reach your own content.
  • Async deep-search jobs return an HMAC token bound to your customer id; /v1/jobs/{token} only un-wraps it for the same customer, so job ids can’t be guessed across tenants.
  • General traffic only: Twin Browser is not PHI-eligible, so X-PHI:true returns phi_blocked.

Good to know

  • · Deep search is asynchronous — /v1/search with depth:"deep" returns a job token to poll at /v1/jobs/{token}; shallow search is synchronous.
  • · The captcha-solving and agentic-automation surface (run, live, skills, monitors) is intentionally not exposed — off-posture for a compliance product.
curl
# 1 — ingest sources into a collection
curl https://cloudsitus.com/api/v1/etl \
  -H "Authorization: Bearer $PHI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "sources": ["https://example.com/handbook"], "collection": "handbook" }'

# 2 — semantic query over that collection
curl https://cloudsitus.com/api/v1/etl/query \
  -H "Authorization: Bearer $PHI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "what is the refund window?", "collection": "handbook" }'
response
x-phi-routed: etl-query/EU/general
x-phi-upstream: twin-browser
x-phi-cost-micro: 4000
{ "matches": [{ "text": "Refunds within 30 days...", "score": 0.82 }],
  "collection": "handbook" }

FAQ

Common questions

Embeddings & searchAPI referenceAll capabilities
Where does my ingested data live?
In Twin Browser, the upstream that runs the pipeline and hosts the vector store. CloudSitus is a stateless proxy — it authenticates your key, namespaces your collection, forwards with our server key and bills pass-through. It holds no vector store, no collection list and no job table.
Can other customers see my content?
No. Every customer’s collection is namespaced server-side from your API key identity, never from the request body, so a query is scoped to your namespace and can’t reach another tenant’s rows. Async jobs return a customer-bound token, not the raw upstream job id.
Can I run ETL or search on PHI?
No. Twin Browser is not a PHI-eligible host, so any X-PHI:true request returns phi_blocked — use ETL and search for general content only.
How is it priced?
Per use. Each call is billed on the credits it reports, at 1 USD = 1000 credits. Async jobs settle once, on the first terminal poll.

Ready when you are

Put etl & search in production — without giving up your data.

Spin up a key in minutes. The residency and PHI posture above arrives unchanged.

Get startedSee pricing

Prepaid credits from $10 · No subscription · No data retained