> ## Documentation Index > Fetch the complete documentation index at: https://deepline.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Use GovFiles in Deepline > Use company and officer search for discovery, company lookup for a known registry identifier, and local-business batches to resolve up to 500 physical. [Human guide: work with your agent →](https://deepline.com/docs/human/providers/govfiles/guide.md) Inspect one GovFiles action before starting provider-backed work. Your first result is a verified input and output contract. ## Provider-specific requirements Use company search or officer search to discover US entities across supported jurisdictions. Use company lookup when the jurisdiction code and registry number are already known. For physical locations, submit a local-business batch with 1–500 rows and poll the returned batch id until it is `succeeded` or `failed`. successful results include the complete result document inline. GovFiles uses an `X-API-Key` credential. GovFiles provider charges remain on the connected account, while Deepline separately charges Deepline credits for billable search, direct lookup, and matched local-business operations. ### OpenSOSData migration For an OpenSOSData-style legal-entity lookup with `entity_name` and `state`, use `govfiles_search_companies_v2` with `q` set to the entity name and the state's GovFiles jurisdiction code (for example, `us_de`), then use `govfiles_get_company_v2` with the returned jurisdiction and registry number. Use `govfiles_search_officers_v2` when the workflow needs person-to-company relationships. For local-business ownership enrichment, use `govfiles_create_local_business_batch`, then `govfiles_get_local_business_batch`. Each batch accepts 1–500 rows. Split a 1,000-row request into at least two batches. Each row requires a business name and address. Name and state alone do not satisfy location matching. Results can include operator legal names, restaurants, and people. Inspect the action contract for Deepline prices and billable outcomes. Your connected GovFiles account has separate billing rules. ## Find an applicable action Confirm your effective workspace, then search the live catalog: ```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} deepline auth status --json deepline search "GovFiles" --type tools --json ``` Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically. ## Inspect the selected contract Replace `` with the identifier returned by discovery: ```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}} deepline describe --json ``` These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract. ## Prepare one reviewed input Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow [Write Plays](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md). > [!TIP] > > Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.