connect at an https:// URL, pass an API key, and every
table and search call after that is the one you’d write for connect("./data") or
connect("s3://…").
1
Before you start
You need two things from the Infino Cloud console at platform.infino.ws:
- An API key — a string beginning
inf_…. Treat it like a password. See Authentication. - Your endpoint URL, in the form
https://api.platform.infino.ws/<database>. The scheme and host identify the service; the last path segment is the database this connection targets (for examplehttps://api.platform.infino.ws/my-app). One connection is bound to one database.
2
Install
The packages are the same as for local use. Rust needs the
remote feature for the
hosted transport.3
Connect
Pass the endpoint URL and your API key. The key can be given explicitly or read from the
With
INFINO_API_KEY environment variable, in which case the key argument is optional.INFINO_API_KEY set in the environment, drop the key argument:
connect("https://api.platform.infino.ws/my-app") picks it up.4
Provision your database
Create the database this connection targets, once, from code:
create_database registers the database named in your connection URL, so you can go
from a fresh API key to a working table without leaving your editor. It fails if the
database already exists, so skip this step if you already created the database in the
console. On a local connection the same call is a harmless no-op, so setup code
written for Infino Cloud also runs against ./data or s3://… unchanged.5
Create a table, add data, search
From here, every call is exactly what you’d write locally.
On Infino Cloud,
vector_search and hybrid_search require an explicit projection
argument naming the columns to return (for example ["_id", "body"]). bm25_search
does not. This is the one call-site difference from a local connection.vector_search, hybrid_search, count, query_sql, update, delete,
list_tables, and drop_table all work the same way over the hosted connection. For
the full search surface see Search; for tables and schema see
Tables.Local to hosted is a one-line change
The hosted connection is the local API with a different target. A program written againstconnect("./data") moves to Infino Cloud by changing only the connect line:
vector_search and hybrid_search take an explicit projection.
Table maintenance (
optimize and gc) is handled for you on Infino Cloud, so you
never call it from the client.See also
- Authentication — API keys, the
Authorizationheader, and rotation. - Errors & retries — the transient
503a cold-starting database returns, and how to retry it. - Search — BM25, vector, hybrid, and SQL.
- Tables — schema, indexes, and mutations.
- Connect & storage — local and object-storage backends.
- CLI — connect to Infino Cloud from the terminal with
--api-keyandcreate-database. - MCP server — serve your hosted database to an AI agent (Claude, Cursor, …) with
INFINO_MCP_URI+INFINO_API_KEY.
