Loading...

Let the agent load your data

In the other lessons you build the list yourself. Here the agent does it — you describe what you want in plain English and it makes the calls.

Ask for a list, with data

With a write-capable key connected, you can just ask:

You: Create a list called products and load these ten items into it. Make the name and description searchable, and brand and price filterable.

Agent: Done — I created the products list, added ten records, and set name and description as searchable, brand and price as filters. It's live; want me to try a search?

Behind that, the agent made two ordinary Search Stack calls: one to create the list, one to load the records and set up the fields from your data. It chose the tools; you chose the outcome. The same works for "import the file at this URL" or "add these rows to my existing list".

Or from code

The agent's tools map one-to-one to the API, so if you'd rather script it, the same two moves are two requests. Create the list:

POST https://api.searchstack.dev/list
X-API-Key: {your key}
Content-Type: application/json

{ "account_name": "Demo", "list_name": "products", "subscription_name": "Free" }

Then load the records, letting Search Stack create the fields from the data:

POST https://api.searchstack.dev/search-result/Demo/products/with-fields
X-API-Key: {your key}
Content-Type: application/json

[
  { "name": "Trail Runner 2", "description": "lightweight road-to-trail shoe", "brand": "Vireo", "price": 119 },
  { "name": "Cloud Mesh Tee",  "description": "breathable merino training top", "brand": "Vireo", "price": 44 }
]

That's the exact call the agent made on your behalf — it just decided the field roles from what you asked. Whether you type the request to Claude or POST it yourself, the same list ends up searchable.

Go deeper: Lists, fields, and importing records in the reference.

Top