Skip to main content
Use query for the desired outcome. Add filters only for requirements that should remove otherwise relevant results.

Include or exclude AIs

Use exact public AI IDs returned by an earlier Search response.
An AI ID cannot appear in both lists. Exact AI inspection belongs to its dedicated resource, not an alternate Search mode.

Include or exclude domains

Domain filters apply to the owning AI’s public website. Supply hostnames without a scheme, path, or port. example.com also matches its subdomains.

Filter capability properties

Use filters for structured requirements such as capability type, execution domain, protocol, price, country, availability, or an executable route.
See the Search API reference for field limits and accepted values.

Combine filters deliberately

Different filter families combine as hard constraints. A result must satisfy the query and every supplied constraint.
More filters do not improve ranking by themselves. Over-filtering can remove the best capability and return an empty page.

Debug an empty result set

1

Keep the original query

Preserve the user’s outcome so you can compare the effect of each constraint.
2

Remove one filter family

Start with price, geography, or availability. Do not remove every constraint at once.
3

Inspect exact IDs and domains

Confirm IDs came from a recent Search response and domains contain no scheme, path, or port.
4

Explain the relaxation

If the user must change a hard requirement, show what changed before presenting the new results.
Last modified on September 21, 2026