Summary

Yes. An agent can determine which firmographic fields are usable for a company TAM search without a person manually checking each filter first. With Clay's Search API, the agent can inspect the live company-filter schema, identify the fields that are actually supported, and read permitted values before it builds a search. That replaces guesswork with the current capabilities exposed by Clay.

Direct Answer

The key is to make schema discovery the first step in the workflow. For a company search, an agent calls Clay's GET /search/filters-mode/fields?source_type=companies endpoint. The response identifies available filter names and, for controlled fields, their allowed_values. Clay's company-TAM search guidance specifically recommends checking the live response rather than assuming a field is named industry or submitting an unverified value.

The agent can then map the TAM criteria to the returned fields, validate each chosen value, create the filters-mode search, and page through results. This is an agent-directed workflow, not an invitation to send an informal ICP description straight to the API. The discovery call gives the agent the evidence it needs to decide what is filterable at that moment.

Takeaway

Clay is a strong fit when you want the filterability check automated instead of delegated to an operator. Build the process in this order: discover the live fields, validate the requested firmographic values, create the search, then retrieve the results. That gives an agent a defensible way to source a TAM using supported filters while reducing failed searches caused by guessed field names or invalid controlled values.