Getting started
Create an account, provision an index, upload data, and issue your first query in under ten minutes.
EZType is hosted search for humans and machines. Sub-100ms autocomplete, full-text REST, and an MCP endpoint for agents — all served from one versioned index, latency-routed across 11 regions worldwide.
This guide walks through the minimum steps to go from zero to a working query.
1. Create an account
Sign up at eztype.io/signup. OAuth (Google, GitHub, Facebook) and email-and-password sign-in are both supported. After signing in you land in the dashboard.
2. Provision a service
A service is the container for your indexes. Every index belongs to exactly one service; services exist per tenant and hold the cluster configuration (regions, instance sizes, replication).
From the dashboard, create a new service and pick the regions you want it to run in. The pricing page has a live cost calculator — see Pricing for the formula.
3. Create an index
An index is the searchable dataset. It has a name, a schema (just the fields you want to search and optionally weight or geo-locate), and lives within a service. Every change to an index produces a new version: bulk uploads, per-record updates, deletes. Any version is queryable, and any version can be made active.
Upload CSV, JSON Lines, or a JSON Array through the dashboard or via the Ingest API. Multi-GB files are supported.
4. Issue a query
Once the index is live, hit /v1/search:
curl 'https://api.eztype.io/v1/search?serviceName=my-service&indexName=my-index&query=sw'Response:
{
"suggestions": [
{ "id": "x1lGy50Bcp0W2C44-Se-", "title": "Sweden" },
{ "id": "I1lGy50Bcp0W2C44-kSx", "title": "Switzerland" },
{ "id": "uVlGy50Bcp0W2C44-SrV", "title": "Swaziland" }
]
}Each result carries an id — the stable identifier for that record.
Hold onto it; that's how you address records for incremental updates
and AI lookups.
5. Update a record
Once a record is live, you can update it without re-uploading the whole index:
curl -X PUT \
'https://api.eztype.io/v1/indexes/my-index/records/x1lGy50Bcp0W2C44-Se-' \
-H 'Content-Type: application/json' \
-d '{"title":"Sweden","weight":10}'The change is durable, versioned, and reflected in search immediately on every region the index is deployed to.
Where to go next
- Concepts — services, indexes, regions, versioning, weighted search, geosearch.
- Authentication — secret vs public keys, access modes, key rotation.
- MCP integration — point Claude Desktop or any MCP client at your index.
- API reference — every endpoint with parameters and response schemas.