Skip to main content
Human guide: work with your agent → Inspect one Akta action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Start with akta_company_search. It accepts a company name, website, or Akta UUID and avoids guessing which identifier a later company action will resolve. Use akta_industry_search to translate a plain-language topic into Akta industry codes before constructing an industry-filtered news request. Treat the two search actions as resolvers:
  • inspect all returned matches.
  • prefer an exact website match over a name-only match.
  • keep the Akta UUID for subsequent lookups.
  • handle both an empty data array and a no-result status.
If company search returns no match, do not work around the disabled Company Addition action. akta_request_status accepts only a request ID created through an approved Akta flow. Do not work around an unavailable action. Paid actions are intentionally gated until an internal account proves the runtime charge and response shape. For Product Reviews, do not convert the products array into a comma-separated string. The wire format repeats the query key. For Company Data and News filters, preserve comma-separated strings exactly as documented.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
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. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.