Pay-per-result SAM.gov contracts, SEC EDGAR filings, USAspending awards and GLEIF LEI lookups.
Scored across 11 tools
Each tool has a clearly distinct purpose: actor-run lifecycle operations, storage retrieval, and specific external data-source lookups are well separated. There is little risk of an agent confusing one tool with another.
The tool names are readable and all use kebab-case, but conventions are mixed: platform tools use unprefixed verb-object names while domain tools use a 'gouda_studios--' prefix and mostly resource-phrase names. The pattern is understandable but not consistent.
Eleven tools is a well-scoped set for a server combining actor/storage support with multiple data-source integrations. Each tool appears to earn its place without excessive overlap.
Core read operations are present, but the actor-run lifecycle lacks a start/list operation, and dataset/key-value storage support is read-only with no listing or write operations. These gaps limit end-to-end workflows even though individual lookups are covered.
Requests abort of an Actor run that is starting or running. No effect if the run already finished.
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | Actor run id. | |
| gracefully | No | If true, request a graceful abort. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuine context beyond them: the state-dependent no-op behavior and the word "Requests" implying the abort is an asynchronous request rather than a guaranteed immediate kill. It does not say what happens to a partially written run's output, which would have earned a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, zero filler, and the primary action is front-loaded with the caveat immediately after. Nothing is redundant with the title or with structured fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. For a two-parameter destructive tool with full annotation coverage, the definition covers the essential semantics; the only gap is the graceful-abort tradeoff, which the schema partially carries.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so both parameters are already documented in the schema, making 3 the baseline. The description adds the run-state context that determines whether runId matters at all, but says nothing about the gracefully flag beyond what its schema description already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb and resource ("Requests abort of an Actor run") plus a scope qualifier ("starting or running"), which is clearly distinguishable from the unrelated sibling tools listed. It stops short of differentiating within a family of run-management tools, since no such siblings appear here.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It states an explicit pre-condition (run must be starting or running) and an explicit no-op case ("No effect if the run already finished"), which is real when-to-use guidance. It does not discuss when to choose a graceful vs. immediate abort, leaving the main usage decision to the schema flag.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns status, storages, stats, and a short summary for one Actor run. Use after starting a run, or with waitSecs to wait for a terminal status.
| Name | Required | Description | Default |
|---|---|---|---|
| runId | Yes | Actor run id. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds the non-obvious trait that the call can block for a while when waitSecs is supplied, returning once the run reaches a terminal status. It stops short of stating what happens if the wait times out or the runId is unknown.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler, with the return contents front-loaded and the usage guidance second. Every clause carries information the agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so the description need not detail return values, and annotations cover the safety profile; the blocking-wait behavior is disclosed. For a two-parameter tool this is nearly complete, with only edge-case behavior (timeout, missing run) unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both runId and waitSecs are already documented, giving a 3 baseline. The description's "wait for a terminal status" adds modest intent context for waitSecs but no format, bounds, or interaction detail beyond the schema's own 0-45 range note.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Returns status, storages, stats, and a short summary for one Actor run" gives a specific verb (returns) plus the exact resource (a single Actor run) and even enumerates the payload contents. It cleanly separates from abort-actor-run by being a read rather than a control action, though it never names that sibling explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Use after starting a run, or with waitSecs to wait for a terminal status" tells the agent both the lifecycle position (post-start) and the polling-vs-blocking mode. There is no explicit when-not guidance or named alternative, which keeps it short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns rows from a dataset produced by an Actor run. Use when you have a datasetId and need the result items.
| Name | Required | Description | Default |
|---|---|---|---|
| desc | No | If true, return newest items first. | |
| omit | No | Comma-separated fields to omit. | |
| clean | No | If true, skip empty items and hidden fields. | |
| limit | No | Maximum number of items to return. | |
| fields | No | Comma-separated fields to include. | |
| offset | No | Number of items to skip. | |
| flatten | No | Comma-separated fields to flatten. | |
| datasetId | Yes | Dataset id or username~dataset-name. |
| Name | Required | Description |
|---|---|---|
| items | Yes | Dataset items |
| limit | Yes | Limit used for pagination |
| offset | Yes | Offset used for pagination |
| summary | Yes | Summary of the result |
| nextStep | Yes | One follow-up action with tool name |
| datasetId | Yes | Dataset ID |
| itemCount | Yes | Number of items returned |
| totalItemCount | Yes | Total items in dataset |
| apifyConsoleUrl | No | Personalized Apify Console link to the dataset; present. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds only that the dataset originates from an Actor run. It says nothing about pagination behavior, default limits, ordering defaults, or what happens with an invalid/empty datasetId.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the purpose followed by the usage condition, with no filler. It is arguably too terse for an eight-parameter paginated read, but nothing in it is wasted or misplaced.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-shape explanation is not required, and all parameters are covered by the schema. However, for a paginated, field-shaping read tool, the description omits any hint about paging through large datasets or how limit/offset interact, leaving the agent to infer retrieval strategy.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all eight parameters (limit, offset, desc, clean, fields, omit, flatten, datasetId) are already documented in the schema. The description adds no meaning on top of that, which is the expected baseline when the schema does the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: 'Returns rows from a dataset produced by an Actor run.' An agent can tell this is a read of dataset items rather than an Actor run or key-value store operation. It does not name a sibling it is not, but no sibling in the list is a closely competing dataset-item reader.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use when you have a datasetId and need the result items' gives a clear precondition and intent, which implies when to reach for it. It offers no exclusions, no mention of what to use when you do not yet have a datasetId (e.g. fetching the run first), and no guidance among the field-shaping options.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns one record from a key-value store by store id and record key. Use for INPUT, OUTPUT, or other named records.
| Name | Required | Description | Default |
|---|---|---|---|
| recordKey | Yes | Record key to retrieve. | |
| keyValueStoreId | Yes | Key-value store id or username~store-name. |
| Name | Required | Description |
|---|---|---|
| key | Yes | Record key |
| value | Yes | The stored value (JSON, text, or binary) |
| summary | Yes | Summary of the result |
| contentType | No | MIME type of the stored value |
| keyValueStoreId | Yes | Key-value store ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the notion of named record types and no failure semantics (e.g., missing key or wrong store), which is the one piece of behavior an agent could genuinely use here.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with the core action front-loaded and no filler. The second sentence is only mildly informative but is cheap and points at intended record key values.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not explain return values, and annotations cover the safety profile; parameter documentation is complete in the schema. The only real omission is error/not-found behavior for a lookup tool, which keeps it from a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both parameters are documented, including the 'username~store-name' form of the store id in the schema. The description's 'by store id and record key' merely restates the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource ('Returns one record from a key-value store') and names the two lookup dimensions (store id, record key), so an agent knows exactly what the tool fetches. It does not need to differentiate from siblings, which are entirely unrelated integrations, but it also does not call that out.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use for INPUT, OUTPUT, or other named records' gives a hint about which record keys are meaningful, implying the tool is for retrieving named payloads. There is no explicit when-not guidance, no alternative retrieval tool named, and no statement about what happens for a missing key.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Looks up a company LEI by name, or returns LEI details by identifier, from the GLEIF registry (legal name, status, jurisdiction, addresses, parents). Use for company identity checks.
| Name | Required | Description | Default |
|---|---|---|---|
| leis | No | Optional 20-character LEIs to fetch directly. | |
| country | No | Optional ISO 2-letter country of the legal address, . | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| activeOnly | No | If true, skip archived notices. | |
| maxResults | No | Maximum notices to return. | |
| companyNames | No | Legal names to look up, e.g. ["Apple Inc.","Siemens. | |
| includeParents | No | true (default) = add direct and ultimate parent (LEI. | |
| maxMatchesPerName | No | How many candidate entities to return per name or. | |
| registrationNumbers | No | Optional company-registry numbers as reported to GLEIF. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, yet the description frames the tool purely as a read-only registry lookup with no hint of side effects, cost, or actor-run behavior. The waitSecs/wait semantics of an async run are also never surfaced. The description's 'lookup/return' framing is at odds with the destructive annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the primary capability and then the intended use case. No wasted wording, though the second sentence is thin enough to border on filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need no explanation, and the description covers both lookup modes for a 9-parameter all-optional tool. It omits the asynchronous run/wait behavior and any note on result limits, which leaves a small completeness gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with all nine parameters documented, so the schema carries parameter meaning. The description only implies the name-vs-LEI modes (companyNames vs leis) and adds no format or behavior detail beyond that, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States specific verbs and resource: 'Looks up a company LEI by name, or returns LEI details by identifier, from the GLEIF registry', and enumerates the returned fields (legal name, status, jurisdiction, addresses, parents). The two lookup modes are clearly distinguished, so an agent can tell this apart from the sibling feed/search tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit use context: 'Use for company identity checks', which tells the agent the scenario this tool serves. It does not name when-not-to-use or point to alternatives, so it falls short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns Google Trends interest-over-time, region interest, related queries/topics, and daily trends for keywords. Use for search-interest research.
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | ISO code like US, GB, DE, or US-CA. Leave empty . | US |
| category | No | Google Trends category number, 0 for all categories. | |
| language | No | Interface language for names, e.g. en-US, de, es. | en-US |
| maxTerms | No | Stop after this many terms. | |
| property | No | Which Google search the trend data comes . | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| timeRange | No | How far back to look. | today 12-m |
| searchTerms | No | Keywords or phrases. Each one is fetched separately . | |
| trendingNow | No | Adds one row per currently trending search in the chosen. | |
| relatedTopics | No | Top and rising related topics. | |
| relatedQueries | No | Top and rising related searches. | |
| interestByRegion | No | 0-100 interest for each subregion. | |
| interestOverTime | No | Timeline of 0-100 interest values. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, yet the description never acknowledges the tool triggers a run that consumes resources or that 'destructive' behavior is possible, nor does it explain the waitSecs polling semantics. With annotations present the bar is lower, but a destructiveHint=true scraper with no behavioral note leaves an agent unable to judge side effects or cost.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the returned data types before the usage hint. There is no filler or redundancy, though the second sentence is thin enough that it adds little weight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and there are no required parameters. However, for a 13-parameter, open-world, destructive-flagged tool, the description is silent on run mechanics, cost, and how the output toggles combine, leaving moderate gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all 13 parameters (geo, timeRange, property, trendingNow flags, etc.) are already documented inline. The description adds only the generic notion of 'keywords' and 'regions' without clarifying parameter interactions such as per-term fetching or the effect of the boolean toggles on output shape, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Returns') and enumerates concrete resources: interest-over-time, region interest, related queries/topics, and daily trends for keywords. That clearly distinguishes it from all listed siblings, which cover filings, awards, transcripts, and actor-run management. It loses a point only because it doesn't state the source mechanism is a Google Trends scrape/actor run.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use for search-interest research' implies a context but names no alternatives, prerequisites, or exclusions. Since no sibling tool overlaps with search-interest data, the lack of explicit routing is tolerable, but the guidance remains implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns SAM.gov federal contract opportunities as JSON, filterable by keyword, NAICS, set-aside, notice type, agency, and state. Use for new or matching notices.
| Name | Required | Description | Default |
|---|---|---|---|
| states | No | Optional 2-letter US state codes. | |
| onlyNew | No | If true, return only notices not seen before. | |
| keywords | No | Optional free-text search terms. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| setAsides | No | Optional small-business set-aside codes. | |
| activeOnly | No | If true, skip archived notices. | |
| maxResults | No | Maximum notices to return. | |
| naicsCodes | No | Optional 6-digit NAICS codes. | |
| noticeTypes | No | Optional SAM notice type codes. | |
| agencyContains | No | Optional agency name substring. | |
| includeDetails | No | If true, fetch full notice details. | |
| includeContacts | No | If true, include contracting officer contacts. | |
| postedWithinDays | No | Only notices from the last N days; 0 = no limit. | |
| minDaysUntilResponse | No | Minimum days remaining until response deadline. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, yet the description presents this as a plain data fetch and never reconciles that profile — no mention that it runs an actor, writes a dataset, blocks for up to waitSecs, or hits SAM.gov rate/API-key constraints. It also omits that onlyNew is stateful (depends on prior runs having recorded seen notices), which materially changes behavior between calls.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the return type and filter surface, with no filler. The second sentence is thin but not wasteful; the only cost is that the brevity leaves real gaps elsewhere rather than padding this sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need not be explained, but a 14-parameter, zero-required tool with stateful flags, a blocking wait, and a destructive/actor-run annotation profile needs more than two sentences. Key call-shaping details — defaults that silently narrow results (activeOnly=true, includeDetails=true), and the fact that a 30s wait may return partial runs — go unmentioned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every one of the 14 parameters already carries its own documentation; the description's list of filter dimensions merely mirrors a subset of them. It adds no meaning beyond the schema, e.g. nothing on how maxResults interacts with waitSecs or on the semantics of the notice-type and set-aside codes.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource ("Returns SAM.gov federal contract opportunities as JSON") and enumerates the filter dimensions (keyword, NAICS, set-aside, notice type, agency, state), so the agent knows exactly what data comes back. It does not differentiate from the closest sibling, gouda_studios--usaspending-awards-search, which covers a related but distinct dataset (historical awards vs. active opportunities).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Use for new or matching notices" is the only usage signal and it is too vague to route an agent: it does not say when to prefer this over usaspending-awards-search, nor when to use onlyNew versus postedWithinDays. No exclusions, prerequisites, or alternative tools are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns SEC EDGAR filings for tickers or CIKs (8-K, 10-Q, 10-K, Form 4, Form D, S-1) with filing dates and document links. Use for company filing monitoring.
| Name | Required | Description | Default |
|---|---|---|---|
| ciks | No | Optional SEC Central Index Keys, e.g. ["320193"]. Leave. | |
| onlyNew | No | If true, return only notices not seen before. | |
| tickers | No | Optional stock tickers, e.g. ["AAPL","NVDA"]. Resolved. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| formTypes | No | Form types to include, . | |
| maxResults | No | Maximum notices to return. | |
| contactEmail | No | Optional. SEC asks automated clients to identify. | |
| filedWithinDays | No | Only filings from the last N days. 0 = no limit (company. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations declare readOnlyHint=false and destructiveHint=true, which is a surprising profile for a 'returns filings' feed, and the description does nothing to explain or reconcile it (e.g., that invoking it starts a billable actor run that writes to a dataset). It also silently omits the async run model implied by waitSecs and the stateful filtering implied by onlyNew, so the agent cannot tell that repeated calls with onlyNew=true yield different results.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with the resource and its supported form types front-loaded, followed by a usage cue. No filler, though the form-type list is somewhat redundant with the schema title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and covers return shape, so the description needn't explain results, and safety hints are in annotations. But for an 8-parameter, run-based tool with zero required inputs, the description leaves the default invocation and the meaning of an empty parameter set unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all eight parameters; the description only echoes the tickers/CIKs inputs and form-type list. Baseline 3 applies — no added syntax, resolution rules, or guidance on interplay between filedWithinDays and onlyNew.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names a specific verb and data source ('Returns SEC EDGAR filings'), and enumerates the concrete form types (8-K, 10-Q, 10-K, Form 4, Form D, S-1) plus the two query keys (tickers/CIKs). This makes it trivially distinguishable from the other sibling feeds (GLEIF, SAM.gov, USAspending), though it never names a sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use for company filing monitoring' gives a use-case frame, but there is no when-not guidance, no mention of what to do if you only have a company name, and no statement of which of tickers vs ciks to supply (or what happens if neither is given, since all 8 params are optional).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Searches USAspending.gov federal awards by keyword, recipient, agency, NAICS, state, date, and amount. Use to find contracts and grants.
| Name | Required | Description | Default |
|---|---|---|---|
| states | No | Optional 2-letter US state codes. | |
| endDate | No | YYYY-MM-DD. Defaults to today. | |
| onlyNew | No | If true, return only notices not seen before. | |
| keywords | No | Optional free-text search terms. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| awardType | No | contracts (default), idvs, grants, loans. | contracts |
| maxAmount | No | Optional upper bound on award amount. | |
| minAmount | No | Optional lower bound on award amount. | |
| startDate | No | YYYY-MM-DD. Defaults to 90 days ago. USAspending data. | |
| maxResults | No | Maximum notices to return. | |
| naicsCodes | No | Optional 6-digit NAICS codes. | |
| recipientNames | No | Optional company or organization names (or UEIs), . | |
| awardingAgencies | No | Optional top-tier agency names exactly as USAspending. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames this as a passive read ('Searches... Use to find'), while the annotations declare readOnlyHint=false and destructiveHint=true, leaving the agent with two conflicting pictures of the tool's side effects. It also omits all behavioral facts that matter here: that a run is launched, that waitSecs (0-45s) bounds how long it blocks, and that results may be partial if the run doesn't finish.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler, front-loading the resource and searchable dimensions before the usage hint. It is efficiently written, though the terseness comes at the cost of the behavioral detail noted above.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value explanation is not required, but for a 13-parameter tool with an actor-run wrapper the description should still surface blocking behavior and partial-result risk. As written it is adequate for choosing the tool but thin for invoking it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every one of the 13 parameters is already documented in the schema, making 3 the baseline. The description's facet list mirrors the schema fields without adding format, default, or interaction semantics (e.g., default 90-day window, onlyNew, awardType enum).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Searches USAspending.gov federal awards') and enumerates the queryable facets (keyword, recipient, agency, NAICS, state, date, amount), so the agent knows exactly what data domain this covers. Sibling differentiation is implicit only via the domain name (vs. sam-gov-opportunities-feed, sec-edgar-filings-feed), and the description never explicitly says how it differs from the SAM.gov opportunities tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use to find contracts and grants' gives a purpose but no when-to-use vs. when-not guidance and never names an alternative tool. The nearest sibling (sam-gov-opportunities-feed) is about open opportunities rather than awarded spending, yet the description does nothing to route an agent between them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Extracts public emails, phones, social links, and addresses from a list of websites, one deduplicated row per site. Use for contact discovery on public pages.
| Name | Required | Description | Default |
|---|---|---|---|
| checkMx | No | Adds a free DNS check that each email domain can receive. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| startUrls | Yes | Websites or domains to extract contacts from, one per. | |
| defaultCountry | No | Two-letter country code used to read local phone numbers. | US |
| maxPagesPerSite | No | How many pages to read on each site, starting with . | |
| respectRobotsTxt | No | Skip pages that a site's robots.txt asks crawlers not . | |
| proxyConfiguration | No | Optional. Most business sites work without a proxy. Turn. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds one behavioral fact not in structured fields — results are deduplicated to one row per site — but omits the operationally important traits: this starts a billable actor run, waitSecs (0–45s) caps how long it blocks so output may be partial, and robots.txt is honored by default. With annotations carrying the safety load, this is an adequate-but-thin addition.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler, with the extraction scope and output granularity front-loaded before the usage hint. There is no redundancy with the title or schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema exists, so return values need not be explained, and parameter documentation is fully handled by the schema. However, for an open-world crawler with a nested proxy config and a 45-second blocking cap, the description should warn that runs can return partial results or time out and that credits are consumed — context an agent needs to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every one of the seven parameters, including the nested proxyConfiguration object, is already documented in the schema. The description only restates that the input is a list of websites and adds no guidance beyond it, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb (extracts) and enumerates concrete resources (public emails, phones, social links, addresses) plus the input shape (a list of websites) and output shape (one deduplicated row per site). Nothing in the sibling list (YouTube transcripts, SEC filings, LEI lookup, trends) overlaps, so an agent can immediately tell this is the contact-discovery tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Use for contact discovery on public pages" gives a positive usage cue and implicitly scopes it to public data, but there is no when-not guidance, no mention of what to do if a site yields nothing, and no routing to siblings (e.g., running the actor first via get-actor-run). Usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Returns YouTube video or Short transcripts as plain text, timestamped text, segments, or SRT. Use when you need captions or spoken content from a video URL.
| Name | Required | Description | Default |
|---|---|---|---|
| videos | Yes | Watch URLs, youtu.be links, Shorts, live or embed URLs. | |
| waitSecs | No | Seconds to wait for the run to finish (0-45). | |
| languages | No | Language codes in priority order, e.g. en, es, de. If. | |
| maxVideos | No | Stop after this many videos. Example values: 1000 | |
| includeSrt | No | Add an SRT subtitle file as a string. | |
| translateTo | No | Language code to auto-translate the transcript into. | |
| preferManual | No | Use manually created captions over auto-generated ones. | |
| includeSegments | No | Add an array of segments with start time and duration. | |
| proxyConfiguration | No | Optional. Leave off to use our built-in residential. |
| Name | Required | Description |
|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value. |
| runId | Yes | Actor run ID |
| stats | No | Run statistics |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |. |
| actorId | Yes | Stable Apify Actor ID from the run record |
| summary | Yes | Past-tense summary of the run state |
| exitCode | No | Actor process exit code; populated for terminal states. |
| nextStep | Yes | One primary follow-up action with identifiers interpolated |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. |
| actorName | No | "username/actor-name" |
| startedAt | No | ISO timestamp when the run started |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) |
| statusMessage | No | Pass-through from Apify run.statusMessage |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames the tool as a pure retrieval operation ('Returns ... transcripts'), which conflicts with the supplied annotations declaring readOnlyHint=false and destructiveHint=true. The annotations over-warn rather than the description under-warning, but the agent receives no reconciliation. Credit is given for disclosing the four output shapes, which is real behavioral value beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero filler, with the output forms front-loaded before the usage cue. Nothing redundant or buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the format options are covered. However, for a 9-parameter tool with batch input, language priority, translation, and proxy settings, the description says nothing about batch limits, language fallback behavior, or the waitSecs polling semantics an agent must reason about.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter, including the nested proxy object, is already documented structurally; the baseline is 3. The description's mention of SRT and segments implicitly maps to includeSrt and includeSegments but adds no syntax or semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb and resource — 'Returns YouTube video or Short transcripts' — and enumerates the available output forms (plain text, timestamped text, segments, SRT). This is far more specific than the name alone, though it does not explicitly contrast itself with the other Apify actor tools in the sibling list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Use when you need captions or spoken content from a video URL' gives a clear trigger condition, but there is no guidance on when not to use it, no mention of alternatives, and no hint about the batch/language/translation options that would steer an agent's call. Adequate but thin.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
abort-actor-run17 fields changedInput schema / properties / gracefully / descriptionPrevious value: -"If true, the Actor run will abort gracefully with a 30-second timeout."New value: +"If true, request a graceful abort."Input schema / properties / runId / descriptionPrevious value: -"The ID of the Actor run to abort."New value: +"Actor run id."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."get-actor-run17 fields changedInput schema / properties / runId / descriptionPrevious value: -"The ID of the Actor run."New value: +"Actor run id."Input schema / properties / waitSecs / descriptionPrevious value: -"Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT).\n0 returns immediately with the current status. Cap: 45. Default: 30."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."get-dataset-items9 fields changedInput schema / properties / clean / descriptionPrevious value: -"If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true."New value: +"If true, skip empty items and hidden fields."Input schema / properties / datasetId / descriptionPrevious value: -"Dataset ID or username~dataset-name."New value: +"Dataset id or username~dataset-name."Input schema / properties / desc / descriptionPrevious value: -"If true, results are returned in reverse order (newest to oldest)."New value: +"If true, return newest items first."Input schema / properties / fields / descriptionPrevious value: -"Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. \"metadata.url\"); the server auto-flattens parent prefixes."New value: +"Comma-separated fields to include."Input schema / properties / flatten / descriptionPrevious value: -"Comma-separated list of fields to flatten (e.g. flatten=\"metadata\" turns {\"metadata\":{\"url\":\"x\"}} into {\"metadata.url\":\"x\"}). Normally derived automatically from dot-notation in `fields`; specify only as a diagnostic override."New value: +"Comma-separated fields to flatten."Input schema / properties / limit / descriptionPrevious value: -"Maximum number of items to return. Default is 20."New value: +"Maximum number of items to return."Input schema / properties / offset / descriptionPrevious value: -"Number of items to skip at the start. Default is 0."New value: +"Number of items to skip."Input schema / properties / omit / descriptionPrevious value: -"Comma-separated list of fields to exclude from results."New value: +"Comma-separated fields to omit."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."get-key-value-store-record2 fields changedInput schema / properties / keyValueStoreId / descriptionPrevious value: -"Key-value store ID or username~store-name."New value: +"Key-value store id or username~store-name."Input schema / properties / recordKey / descriptionPrevious value: -"Key of the record to retrieve."New value: +"Record key to retrieve."gouda_studios--gleif-company-lei-lookup48 fields changedInput schema / descriptionPrevious value: -"Looks up legal entities worldwide in the official GLEIF Legal Entity Identifier (LEI) database and returns one JSON row per matched company with legal name, status, address, registration number and parent companies. Example: {\"companyNames\":[\"Apple Inc.\"],\"country\":\"US\"} or {\"leis\":[\"HWUPKR0MPOU8FGXBT394\"]}. Pricing: $0.003 per company row."New value: +"Looks up legal entities worldwide in the official GLEIF."Input schema / properties / activeOnly / descriptionPrevious value: -"true (default) = skip lapsed/inactive entities for name and registration searches.\nExample values: true"New value: +"If true, skip archived notices."Input schema / properties / activeOnly / examplesRemoved value: -[
- true
-]Input schema / properties / activeOnly / titleRemoved value: -"Active entities only"Input schema / properties / companyNames / defaultRemoved value: -[]Input schema / properties / companyNames / descriptionPrevious value: -"Legal names to look up, e.g. [\"Apple Inc.\",\"Siemens AG\"]. Exact legal name match first, then fuzzy full-text.\nExample values: [\"Apple Inc.\"]"New value: +"Legal names to look up, e.g. [\"Apple Inc.\",\"Siemens."Input schema / properties / companyNames / examplesRemoved value: -[
- "Apple Inc."
-]Input schema / properties / companyNames / items / descriptionRemoved value: -"Legal names to look up, e.g. [\"Apple Inc.\",\"Siemens AG\"]. Exact legal name match first, then fuzzy full-text."Input schema / properties / companyNames / items / titleRemoved value: -"Company names"Input schema / properties / companyNames / prefillRemoved value: -[
- "Apple Inc."
-]Input schema / properties / companyNames / titleRemoved value: -"Company names"Input schema / properties / country / descriptionPrevious value: -"Optional ISO 2-letter country of the legal address, e.g. US, GB, DE. Improves name matching."New value: +"Optional ISO 2-letter country of the legal address, ."Input schema / properties / country / titleRemoved value: -"Country"Input schema / properties / includeParents / descriptionPrevious value: -"true (default) = add direct and ultimate parent (LEI, name, country) where reported.\nExample values: true"New value: +"true (default) = add direct and ultimate parent (LEI."Input schema / properties / includeParents / examplesRemoved value: -[
- true
-]Input schema / properties / includeParents / titleRemoved value: -"Include parent companies"Input schema / properties / leis / defaultRemoved value: -[]Input schema / properties / leis / items / descriptionRemoved value: -"Optional 20-character LEIs to fetch directly."Input schema / properties / leis / items / titleRemoved value: -"LEI codes"Input schema / properties / leis / titleRemoved value: -"LEI codes"Input schema / properties / maxMatchesPerName / descriptionPrevious value: -"How many candidate entities to return per name or registration number (1-50).\nExample values: 3"New value: +"How many candidate entities to return per name or."Input schema / properties / maxMatchesPerName / examplesRemoved value: -[
- 3
-]Input schema / properties / maxMatchesPerName / titleRemoved value: -"Max matches per name"Input schema / properties / maxResults / descriptionPrevious value: -"Maximum rows overall (1-5000). You pay per row: 100 rows = $0.30.\nExample values: 100"New value: +"Maximum notices to return."Input schema / properties / maxResults / examplesRemoved value: -[
- 100
-]Input schema / properties / maxResults / titleRemoved value: -"Max results"Input schema / properties / registrationNumbers / defaultRemoved value: -[]Input schema / properties / registrationNumbers / descriptionPrevious value: -"Optional company-registry numbers as reported to GLEIF (registeredAs), e.g. a UK Companies House number."New value: +"Optional company-registry numbers as reported to GLEIF."Input schema / properties / registrationNumbers / items / descriptionRemoved value: -"Optional company-registry numbers as reported to GLEIF (registeredAs), e.g. a UK Companies House number."Input schema / properties / registrationNumbers / items / titleRemoved value: -"Registration numbers"Input schema / properties / registrationNumbers / titleRemoved value: -"Registration numbers"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / descriptionPrevious value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--google-trends-explorer35 fields changedInput schema / descriptionPrevious value: -"Fetches Google Trends data per search term: interest over time, interest by region, top and rising related queries and topics, optionally today's trending searches. Example: {\"searchTerms\":[\"ai agents\"],\"geo\":\"US\",\"timeRange\":\"today 12-m\"}. Pricing: $0.004 per search term with data."New value: +"Fetches Google Trends data per search term: interest."Input schema / properties / category / titleRemoved value: -"Category ID"Input schema / properties / geo / descriptionPrevious value: -"ISO code like US, GB, DE, or US-CA. Leave empty for worldwide."New value: +"ISO code like US, GB, DE, or US-CA. Leave empty ."Input schema / properties / geo / titleRemoved value: -"Country or region code"Input schema / properties / interestByRegion / titleRemoved value: -"Interest by region"Input schema / properties / interestOverTime / titleRemoved value: -"Interest over time"Input schema / properties / language / titleRemoved value: -"Language"Input schema / properties / maxTerms / titleRemoved value: -"Max search terms"Input schema / properties / property / descriptionPrevious value: -"Which Google search the trend data comes from."New value: +"Which Google search the trend data comes ."Input schema / properties / property / titleRemoved value: -"Search type"Input schema / properties / relatedQueries / titleRemoved value: -"Related queries"Input schema / properties / relatedTopics / titleRemoved value: -"Related topics"Input schema / properties / searchTerms / descriptionPrevious value: -"Keywords or phrases. Each one is fetched separately and returns one result row."New value: +"Keywords or phrases. Each one is fetched separately ."Input schema / properties / searchTerms / prefillRemoved value: -[
- "bitcoin",
- "ai agents"
-]Input schema / properties / searchTerms / titleRemoved value: -"Search terms"Input schema / properties / timeRange / titleRemoved value: -"Time range"Input schema / properties / trendingNow / descriptionPrevious value: -"Adds one row per currently trending search in the chosen country, with traffic and news links."New value: +"Adds one row per currently trending search in the chosen."Input schema / properties / trendingNow / titleRemoved value: -"Also get today's trending searches"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / descriptionPrevious value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--sam-gov-opportunities-feed62 fields changedInput schema / descriptionPrevious value: -"Returns U.S. federal contract opportunities (RFPs, RFQs, sources sought, award notices) from SAM.gov as one JSON row per notice. All inputs are optional; a good default is {\"keywords\":\"software\",\"postedWithinDays\":7,\"maxResults\":50}. Pricing: pay per event, $0.002 per opportunity row returned."New value: +"Returns U.S. federal contract opportunities (RFPs, RFQs."Input schema / properties / activeOnly / descriptionPrevious value: -"true (default) = skip archived/inactive notices.\nExample values: true"New value: +"If true, skip archived notices."Input schema / properties / activeOnly / examplesRemoved value: -[
- true
-]Input schema / properties / activeOnly / titleRemoved value: -"Active notices only"Input schema / properties / agencyContains / descriptionPrevious value: -"Optional case-insensitive text the agency path must contain, e.g. \"Navy\" or \"Veterans Affairs\"."New value: +"Optional agency name substring."Input schema / properties / agencyContains / titleRemoved value: -"Agency contains"Input schema / properties / apiKeyRemoved value: -{
- "description": "Optional. Your own free api.sam.gov public API key; when set, the Actor reads the official SAM.gov Opportunities API instead of the public search feed.",
- "title": "SAM.gov API key (optional)",
- "type": "string"
-}Input schema / properties / includeContacts / descriptionPrevious value: -"true (default) = include the contracting officer work name, email and phone published on the notice.\nExample values: true"New value: +"If true, include contracting officer contacts."Input schema / properties / includeContacts / examplesRemoved value: -[
- true
-]Input schema / properties / includeContacts / titleRemoved value: -"Include contracting officer contacts"Input schema / properties / includeDetails / descriptionPrevious value: -"true (default) = fetch each notice for NAICS, PSC, set-aside, place of performance, full description and contacts. false = faster, fewer fields.\nExample values: true"New value: +"If true, fetch full notice details."Input schema / properties / includeDetails / examplesRemoved value: -[
- true
-]Input schema / properties / includeDetails / titleRemoved value: -"Fetch full details"Input schema / properties / keywords / descriptionPrevious value: -"Optional free-text search over SAM.gov notice titles and text, e.g. \"cybersecurity\" or \"janitorial services\". Leave empty to return all notices that match the other filters.\nExample values: \"software\""New value: +"Optional free-text search terms."Input schema / properties / keywords / examplesRemoved value: -[
- "software"
-]Input schema / properties / keywords / prefillRemoved value: -"software"Input schema / properties / keywords / titleRemoved value: -"Keywords"Input schema / properties / maxResults / descriptionPrevious value: -"Maximum rows to return (1-10000). You are charged per row returned, so this caps the cost: 100 rows = $0.20 at $0.002/row.\nExample values: 100"New value: +"Maximum notices to return."Input schema / properties / maxResults / examplesRemoved value: -[
- 100
-]Input schema / properties / maxResults / titleRemoved value: -"Max results"Input schema / properties / minDaysUntilResponse / descriptionPrevious value: -"Optional. Skip notices whose response deadline is fewer than N days away, so you only get ones you can still bid on."New value: +"Minimum days remaining until response deadline."Input schema / properties / minDaysUntilResponse / titleRemoved value: -"Minimum days until response deadline"Input schema / properties / naicsCodes / defaultRemoved value: -[]Input schema / properties / naicsCodes / descriptionPrevious value: -"Optional list of 6-digit NAICS industry codes (strings), e.g. [\"541511\",\"541512\"]. A notice matches if it has any of them. Empty = all industries."New value: +"Optional 6-digit NAICS codes."Input schema / properties / naicsCodes / items / descriptionRemoved value: -"Optional list of 6-digit NAICS industry codes (strings), e.g. [\"541511\",\"541512\"]. A notice matches if it has any of them. Empty = all industries."Input schema / properties / naicsCodes / items / titleRemoved value: -"NAICS codes"Input schema / properties / naicsCodes / titleRemoved value: -"NAICS codes"Input schema / properties / noticeTypes / defaultRemoved value: -[]Input schema / properties / noticeTypes / descriptionPrevious value: -"Optional list of notice type codes: o=Solicitation, k=Combined Synopsis/Solicitation, p=Presolicitation, r=Sources Sought, s=Special Notice, a=Award Notice, u=Justification, i=Intent to Bundle, g=Surplus sale. Empty = all types."New value: +"Optional SAM notice type codes."Input schema / properties / noticeTypes / items / enumTitlesRemoved value: -[
- "Solicitation",
- "Combined Synopsis/Solicitation",
- "Presolicitation",
- "Sources Sought",
- "Special Notice",
- "Award Notice",
- "Justification (J&A)",
- "Intent to Bundle",
- "Sale of Surplus Property"
-]Input schema / properties / noticeTypes / titleRemoved value: -"Notice types"Input schema / properties / onlyNew / descriptionPrevious value: -"true = return only notices not delivered in an earlier run with the same filters (state is kept between runs). Use with a schedule for an alert feed."New value: +"If true, return only notices not seen before."Input schema / properties / onlyNew / titleRemoved value: -"Only new since last run (monitor mode)"Input schema / properties / postedWithinDays / descriptionPrevious value: -"Only notices posted or updated in the last N days. 0 = no date limit. Use 1-7 for daily/weekly monitoring."New value: +"Only notices from the last N days; 0 = no limit."Input schema / properties / postedWithinDays / titleRemoved value: -"Posted/updated within (days)"Input schema / properties / setAsides / defaultRemoved value: -[]Input schema / properties / setAsides / descriptionPrevious value: -"Optional small-business set-aside codes, e.g. [\"SBA\",\"8A\",\"SDVOSBC\",\"WOSB\",\"HZC\"]. Empty = any set-aside or none."New value: +"Optional small-business set-aside codes."Input schema / properties / setAsides / items / enumTitlesRemoved value: -[
- "Total Small Business",
- "Partial Small Business",
- "8(a) Competed",
- "8(a) Sole Source",
- "HUBZone",
- "HUBZone Sole Source",
- "SDVOSB",
- "SDVOSB Sole Source",
- "WOSB",
- "WOSB Sole Source",
- "EDWOSB",
- "EDWOSB Sole Source",
- "Veteran-Owned",
- "Veteran-Owned Sole Source"
-]Input schema / properties / setAsides / titleRemoved value: -"Set-asides"Input schema / properties / states / defaultRemoved value: -[]Input schema / properties / states / descriptionPrevious value: -"Optional 2-letter US state codes for the place of performance, e.g. [\"VA\",\"MD\"]. Requires includeDetails=true. Empty = all locations."New value: +"Optional 2-letter US state codes."Input schema / properties / states / items / descriptionRemoved value: -"Optional 2-letter US state codes for the place of performance, e.g. [\"VA\",\"MD\"]. Requires includeDetails=true. Empty = all locations."Input schema / properties / states / items / titleRemoved value: -"Place of performance (state codes)"Input schema / properties / states / titleRemoved value: -"Place of performance (state codes)"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Input schema / requiredRemoved value: -[]Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / descriptionPrevious value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--sec-edgar-filings-feed46 fields changedInput schema / descriptionPrevious value: -"Returns SEC EDGAR filings as one JSON row per filing, from official sec.gov / data.sec.gov endpoints. With tickers or CIKs it reads each company's filing history; with neither it returns the latest market-wide filings of the chosen form types. Example: {\"tickers\":[\"AAPL\",\"TSLA\"],\"formTypes\":[\"8-K\",\"10-Q\"],\"filedWithinDays\":30}. Pricing: $0.002 per filing row."New value: +"Returns SEC EDGAR filings as one JSON row per filing."Input schema / properties / ciks / defaultRemoved value: -[]Input schema / properties / ciks / descriptionPrevious value: -"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave tickers and CIKs empty to get latest filings across all companies."New value: +"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave."Input schema / properties / ciks / items / descriptionRemoved value: -"Optional SEC Central Index Keys, e.g. [\"320193\"]. Leave tickers and CIKs empty to get latest filings across all companies."Input schema / properties / ciks / items / titleRemoved value: -"CIK numbers"Input schema / properties / ciks / titleRemoved value: -"CIK numbers"Input schema / properties / contactEmail / descriptionPrevious value: -"Optional. SEC asks automated clients to identify themselves; this email is sent in the User-Agent header to sec.gov only."New value: +"Optional. SEC asks automated clients to identify."Input schema / properties / contactEmail / titleRemoved value: -"Contact email for SEC User-Agent"Input schema / properties / filedWithinDays / descriptionPrevious value: -"Only filings from the last N days. 0 = no limit (company mode returns the ~1000 most recent).\nExample values: 7"New value: +"Only filings from the last N days. 0 = no limit (company."Input schema / properties / filedWithinDays / examplesRemoved value: -[
- 7
-]Input schema / properties / filedWithinDays / titleRemoved value: -"Filed within (days)"Input schema / properties / formTypes / defaultRemoved value: -[]Input schema / properties / formTypes / descriptionPrevious value: -"Form types to include, e.g. [\"8-K\",\"10-K\",\"10-Q\",\"4\",\"D\",\"S-1\",\"13F-HR\",\"SC 13D\"]. Empty = all forms (company mode only; market-wide mode needs at least one).\nExample values: [\"8-K\"]"New value: +"Form types to include, ."Input schema / properties / formTypes / examplesRemoved value: -[
- "8-K"
-]Input schema / properties / formTypes / items / descriptionRemoved value: -"Form types to include, e.g. [\"8-K\",\"10-K\",\"10-Q\",\"4\",\"D\",\"S-1\",\"13F-HR\",\"SC 13D\"]. Empty = all forms (company mode only; market-wide mode needs at least one)."Input schema / properties / formTypes / items / titleRemoved value: -"Form types"Input schema / properties / formTypes / prefillRemoved value: -[
- "8-K"
-]Input schema / properties / formTypes / titleRemoved value: -"Form types"Input schema / properties / maxResults / descriptionPrevious value: -"Maximum rows (1-5000). You pay per row, so this caps cost: 100 rows = $0.20.\nExample values: 100"New value: +"Maximum notices to return."Input schema / properties / maxResults / examplesRemoved value: -[
- 100
-]Input schema / properties / maxResults / titleRemoved value: -"Max results"Input schema / properties / onlyNew / descriptionPrevious value: -"true = skip filings delivered by an earlier run with the same tickers/CIKs/forms. Use with a schedule for an alert feed."New value: +"If true, return only notices not seen before."Input schema / properties / onlyNew / titleRemoved value: -"Only new since last run"Input schema / properties / tickers / defaultRemoved value: -[]Input schema / properties / tickers / descriptionPrevious value: -"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved to CIKs with the SEC ticker file.\nExample values: [\"AAPL\",\"TSLA\"]"New value: +"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved."Input schema / properties / tickers / examplesRemoved value: -[
- "AAPL",
- "TSLA"
-]Input schema / properties / tickers / items / descriptionRemoved value: -"Optional stock tickers, e.g. [\"AAPL\",\"NVDA\"]. Resolved to CIKs with the SEC ticker file."Input schema / properties / tickers / items / titleRemoved value: -"Tickers"Input schema / properties / tickers / prefillRemoved value: -[
- "AAPL",
- "TSLA"
-]Input schema / properties / tickers / titleRemoved value: -"Tickers"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--usaspending-awards-search58 fields changedInput schema / descriptionPrevious value: -"Returns U.S. federal spending awards (contracts, IDVs, grants, loans) from the official USAspending.gov API, one JSON row per award, largest first. Example: {\"keywords\":[\"cybersecurity\"],\"awardType\":\"contracts\",\"startDate\":\"2026-01-01\",\"maxResults\":50}. Pricing: $0.0015 per award row."New value: +"Returns U.S. federal spending awards (contracts, IDVs."Input schema / properties / awardType / descriptionPrevious value: -"contracts (default), idvs, grants, loans, direct_payments or other.\nExample values: \"contracts\""New value: +"contracts (default), idvs, grants, loans."Input schema / properties / awardType / examplesRemoved value: -[
- "contracts"
-]Input schema / properties / awardType / titleRemoved value: -"Award type"Input schema / properties / awardingAgencies / defaultRemoved value: -[]Input schema / properties / awardingAgencies / descriptionPrevious value: -"Optional top-tier agency names exactly as USAspending lists them, e.g. [\"Department of Defense\",\"Department of Veterans Affairs\"]."New value: +"Optional top-tier agency names exactly as USAspending."Input schema / properties / awardingAgencies / items / descriptionRemoved value: -"Optional top-tier agency names exactly as USAspending lists them, e.g. [\"Department of Defense\",\"Department of Veterans Affairs\"]."Input schema / properties / awardingAgencies / items / titleRemoved value: -"Awarding agencies"Input schema / properties / awardingAgencies / titleRemoved value: -"Awarding agencies"Input schema / properties / endDate / titleRemoved value: -"End date"Input schema / properties / keywords / defaultRemoved value: -[]Input schema / properties / keywords / descriptionPrevious value: -"Optional words to match in award descriptions, e.g. [\"cybersecurity\"].\nExample values: [\"cybersecurity\"]"New value: +"Optional free-text search terms."Input schema / properties / keywords / examplesRemoved value: -[
- "cybersecurity"
-]Input schema / properties / keywords / items / descriptionRemoved value: -"Optional words to match in award descriptions, e.g. [\"cybersecurity\"]."Input schema / properties / keywords / items / titleRemoved value: -"Keywords"Input schema / properties / keywords / prefillRemoved value: -[
- "cybersecurity"
-]Input schema / properties / keywords / titleRemoved value: -"Keywords"Input schema / properties / maxAmount / titleRemoved value: -"Maximum amount (USD)"Input schema / properties / maxResults / descriptionPrevious value: -"Maximum rows (1-10000). You pay per row: 100 rows = $0.15.\nExample values: 100"New value: +"Maximum notices to return."Input schema / properties / maxResults / examplesRemoved value: -[
- 100
-]Input schema / properties / maxResults / titleRemoved value: -"Max results"Input schema / properties / minAmount / titleRemoved value: -"Minimum amount (USD)"Input schema / properties / naicsCodes / defaultRemoved value: -[]Input schema / properties / naicsCodes / descriptionPrevious value: -"Optional NAICS codes (contracts only), e.g. [\"541512\"]."New value: +"Optional 6-digit NAICS codes."Input schema / properties / naicsCodes / items / descriptionRemoved value: -"Optional NAICS codes (contracts only), e.g. [\"541512\"]."Input schema / properties / naicsCodes / items / titleRemoved value: -"NAICS codes"Input schema / properties / naicsCodes / titleRemoved value: -"NAICS codes"Input schema / properties / onlyNew / descriptionPrevious value: -"true = skip awards delivered by an earlier run with the same filters."New value: +"If true, return only notices not seen before."Input schema / properties / onlyNew / titleRemoved value: -"Only new since last run"Input schema / properties / recipientNames / defaultRemoved value: -[]Input schema / properties / recipientNames / descriptionPrevious value: -"Optional company or organization names (or UEIs), e.g. [\"Booz Allen Hamilton\"]. Find a competitor's federal wins."New value: +"Optional company or organization names (or UEIs), ."Input schema / properties / recipientNames / items / descriptionRemoved value: -"Optional company or organization names (or UEIs), e.g. [\"Booz Allen Hamilton\"]. Find a competitor's federal wins."Input schema / properties / recipientNames / items / titleRemoved value: -"Recipient names"Input schema / properties / recipientNames / titleRemoved value: -"Recipient names"Input schema / properties / startDate / descriptionPrevious value: -"YYYY-MM-DD. Defaults to 90 days ago. USAspending data starts 2007-10-01."New value: +"YYYY-MM-DD. Defaults to 90 days ago. USAspending data."Input schema / properties / startDate / titleRemoved value: -"Start date"Input schema / properties / states / defaultRemoved value: -[]Input schema / properties / states / descriptionPrevious value: -"Optional 2-letter state codes, e.g. [\"VA\",\"TX\"]."New value: +"Optional 2-letter US state codes."Input schema / properties / states / items / descriptionRemoved value: -"Optional 2-letter state codes, e.g. [\"VA\",\"TX\"]."Input schema / properties / states / items / titleRemoved value: -"Place of performance states"Input schema / properties / states / titleRemoved value: -"Place of performance states"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / descriptionPrevious value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--website-contact-extractor47 fields changedInput schema / properties / checkMx / descriptionPrevious value: -"Adds a free DNS check that each email domain can receive mail. Flags typos and dead domains.\nExample values: true"New value: +"Adds a free DNS check that each email domain can receive."Input schema / properties / checkMx / examplesRemoved value: -[
- true
-]Input schema / properties / checkMx / titleRemoved value: -"Check email domains for MX records"Input schema / properties / defaultCountry / descriptionPrevious value: -"Two-letter country code used to read local phone numbers that have no +country prefix, e.g. US, GB, DE, AU.\nExample values: \"US\""New value: +"Two-letter country code used to read local phone numbers."Input schema / properties / defaultCountry / examplesRemoved value: -[
- "US"
-]Input schema / properties / defaultCountry / titleRemoved value: -"Default phone country"Input schema / properties / maxPagesPerSite / descriptionPrevious value: -"How many pages to read on each site, starting with the homepage and then the most likely contact pages (Contact, About, Team, Impressum, Support). You pay per site, not per page, so higher values only cost more time.\nExample values: 8"New value: +"How many pages to read on each site, starting with ."Input schema / properties / maxPagesPerSite / examplesRemoved value: -[
- 8
-]Input schema / properties / maxPagesPerSite / titleRemoved value: -"Max pages per site"Input schema / properties / proxyConfiguration / descriptionPrevious value: -"Optional. Most business sites work without a proxy. Turn on Apify Proxy if many sites time out or block requests.\nExample values: {\"useApifyProxy\":false}"New value: +"Optional. Most business sites work without a proxy. Turn."Input schema / properties / proxyConfiguration / examplesRemoved value: -[
- {
- "useApifyProxy": false
- }
-]Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / descriptionPrevious value: -"Select specific Apify Proxy groups to use (e.g., RESIDENTIAL, DATACENTER).\n**DATACENTER:**\nThe fastest and cheapest option. It uses datacenters to change your IP address. Note that there is a chance of being blocked because of the activity of other users.\n\n**RESIDENTIAL:**\nIP addresses located in homes and offices around the world. These IPs are the least likely to be blocked."New value: +"Select specific Apify Proxy groups to use (."Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / items / descriptionRemoved value: -"Proxy group name"Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / items / titleRemoved value: -"Proxy group name"Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / titleRemoved value: -"Apify Proxy Groups"Input schema / properties / proxyConfiguration / properties / proxyUrls / descriptionPrevious value: -"List of custom proxy URLs to be used instead of the Apify Proxy."New value: +"List of custom proxy URLs to be used instead of ."Input schema / properties / proxyConfiguration / properties / proxyUrls / items / descriptionRemoved value: -"Custom proxy URL"Input schema / properties / proxyConfiguration / properties / proxyUrls / items / titleRemoved value: -"Custom proxy URL"Input schema / properties / proxyConfiguration / properties / proxyUrls / titleRemoved value: -"Proxy URLs"Input schema / properties / proxyConfiguration / properties / useApifyProxy / descriptionPrevious value: -"Whether to use Apify Proxy. Set this to false when you want to use custom proxy URLs."New value: +"Whether to use Apify Proxy. Set this to false when you."Input schema / properties / proxyConfiguration / properties / useApifyProxy / titleRemoved value: -"Use Apify Proxy"Input schema / properties / proxyConfiguration / titleRemoved value: -"Proxy"Input schema / properties / respectRobotsTxt / descriptionPrevious value: -"Skip pages that a site's robots.txt asks crawlers not to visit.\nExample values: true"New value: +"Skip pages that a site's robots.txt asks crawlers not ."Input schema / properties / respectRobotsTxt / examplesRemoved value: -[
- true
-]Input schema / properties / respectRobotsTxt / titleRemoved value: -"Respect robots.txt"Input schema / properties / startUrls / descriptionPrevious value: -"**REQUIRED** Websites or domains to extract contacts from, one per line. Examples: https://www.example.com or example.com. Each site becomes exactly one output row.\nExample values: [\"https://apify.com\",\"https://www.python.org\"]"New value: +"Websites or domains to extract contacts from, one per."Input schema / properties / startUrls / examplesRemoved value: -[
- "https://apify.com",
- "https://www.python.org"
-]Input schema / properties / startUrls / items / descriptionRemoved value: -"**REQUIRED** Websites or domains to extract contacts from, one per line. Examples: https://www.example.com or example.com. Each site becomes exactly one output row."Input schema / properties / startUrls / items / titleRemoved value: -"Websites"Input schema / properties / startUrls / prefillRemoved value: -[
- "https://apify.com",
- "https://www.python.org"
-]Input schema / properties / startUrls / titleRemoved value: -"Websites"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--youtube-transcript-extractor54 fields changedInput schema / properties / includeSegments / descriptionPrevious value: -"Add an array of segments with start time and duration.\nExample values: true"New value: +"Add an array of segments with start time and duration."Input schema / properties / includeSegments / examplesRemoved value: -[
- true
-]Input schema / properties / includeSegments / titleRemoved value: -"Include timed segments"Input schema / properties / includeSrt / titleRemoved value: -"Include SRT subtitles"Input schema / properties / languages / descriptionPrevious value: -"Language codes in priority order, e.g. en, es, de. If none match, the first available transcript is returned.\nExample values: [\"en\"]"New value: +"Language codes in priority order, e.g. en, es, de. If."Input schema / properties / languages / examplesRemoved value: -[
- "en"
-]Input schema / properties / languages / items / descriptionRemoved value: -"Language codes in priority order, e.g. en, es, de. If none match, the first available transcript is returned."Input schema / properties / languages / items / titleRemoved value: -"Preferred languages"Input schema / properties / languages / titleRemoved value: -"Preferred languages"Input schema / properties / maxVideos / descriptionPrevious value: -"Stop after this many videos.\nExample values: 1000"New value: +"Stop after this many videos. Example values: 1000"Input schema / properties / maxVideos / examplesRemoved value: -[
- 1000
-]Input schema / properties / maxVideos / titleRemoved value: -"Max videos"Input schema / properties / preferManual / descriptionPrevious value: -"Use manually created captions over auto-generated ones when both exist.\nExample values: true"New value: +"Use manually created captions over auto-generated ones."Input schema / properties / preferManual / examplesRemoved value: -[
- true
-]Input schema / properties / preferManual / titleRemoved value: -"Prefer human-made captions"Input schema / properties / proxyConfiguration / descriptionPrevious value: -"Optional. Leave off to use our built-in residential proxy, included in the price. Set your own only if you want to.\nExample values: {\"useApifyProxy\":false}"New value: +"Optional. Leave off to use our built-in residential."Input schema / properties / proxyConfiguration / examplesRemoved value: -[
- {
- "useApifyProxy": false
- }
-]Input schema / properties / proxyConfiguration / prefillRemoved value: -{
- "useApifyProxy": false
-}Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / descriptionPrevious value: -"Select specific Apify Proxy groups to use (e.g., RESIDENTIAL, DATACENTER).\n**DATACENTER:**\nThe fastest and cheapest option. It uses datacenters to change your IP address. Note that there is a chance of being blocked because of the activity of other users.\n\n**RESIDENTIAL:**\nIP addresses located in homes and offices around the world. These IPs are the least likely to be blocked."New value: +"Select specific Apify Proxy groups to use (."Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / items / descriptionRemoved value: -"Proxy group name"Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / items / titleRemoved value: -"Proxy group name"Input schema / properties / proxyConfiguration / properties / apifyProxyGroups / titleRemoved value: -"Apify Proxy Groups"Input schema / properties / proxyConfiguration / properties / proxyUrls / descriptionPrevious value: -"List of custom proxy URLs to be used instead of the Apify Proxy."New value: +"List of custom proxy URLs to be used instead of ."Input schema / properties / proxyConfiguration / properties / proxyUrls / items / descriptionRemoved value: -"Custom proxy URL"Input schema / properties / proxyConfiguration / properties / proxyUrls / items / titleRemoved value: -"Custom proxy URL"Input schema / properties / proxyConfiguration / properties / proxyUrls / titleRemoved value: -"Proxy URLs"Input schema / properties / proxyConfiguration / properties / useApifyProxy / descriptionPrevious value: -"Whether to use Apify Proxy. Set this to false when you want to use custom proxy URLs."New value: +"Whether to use Apify Proxy. Set this to false when you."Input schema / properties / proxyConfiguration / properties / useApifyProxy / titleRemoved value: -"Use Apify Proxy"Input schema / properties / proxyConfiguration / titleRemoved value: -"Proxy"Input schema / properties / translateTo / descriptionPrevious value: -"Language code to auto-translate the transcript into using YouTube's translation, e.g. en."New value: +"Language code to auto-translate the transcript into."Input schema / properties / translateTo / titleRemoved value: -"Translate to (optional)"Input schema / properties / videos / descriptionPrevious value: -"**REQUIRED** Watch URLs, youtu.be links, Shorts, live or embed URLs, or bare 11-character video IDs.\nExample values: [\"https://www.youtube.com/watch?v=dQw4w9WgXcQ\"]"New value: +"Watch URLs, youtu.be links, Shorts, live or embed URLs."Input schema / properties / videos / examplesRemoved value: -[
- "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
-]Input schema / properties / videos / items / descriptionRemoved value: -"**REQUIRED** Watch URLs, youtu.be links, Shorts, live or embed URLs, or bare 11-character video IDs."Input schema / properties / videos / items / titleRemoved value: -"YouTube video URLs or IDs"Input schema / properties / videos / prefillRemoved value: -[
- "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
-]Input schema / properties / videos / titleRemoved value: -"YouTube video URLs or IDs"Input schema / properties / waitSecs / descriptionPrevious value: -"Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget."New value: +"Seconds to wait for the run to finish (0-45)."Output schema / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the run; present only for Console sessions"New value: +"Personalized Apify Console link to the run; present only."Output schema / properties / exitCode / descriptionPrevious value: -"Actor process exit code; populated for terminal states (especially FAILED)"New value: +"Actor process exit code; populated for terminal states."Output schema / properties / status / descriptionPrevious value: -"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED"New value: +"Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT |."Output schema / properties / storages / descriptionPrevious value: -"Dataset and key-value store metadata, keyed by alias. \"default\" is always the primary entry."New value: +"Dataset and key-value store metadata, keyed by alias."Output schema / properties / storages / properties / datasets / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / additionalProperties / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / descriptionPrevious value: -"Map of dataset alias → metadata. Key \"default\" is always the run's primary dataset."New value: +"Map of dataset alias → metadata. Key \"default\" is always."Output schema / properties / storages / properties / datasets / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the dataset; present only for Console sessions"New value: +"Personalized Apify Console link to the dataset; present."Output schema / properties / storages / properties / datasets / properties / default / properties / inflatedBytes / descriptionPrevious value: -"Approximate uncompressed byte size of the dataset. Use with itemCount to pick limit/fields before fetching."New value: +"Approximate uncompressed byte size of the dataset. Use."Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / descriptionPrevious value: -"JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema."New value: +"JSON Schema for rows in the dataset at."Output schema / properties / storages / properties / keyValueStores / additionalProperties / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / storages / properties / keyValueStores / descriptionPrevious value: -"Map of key-value store alias → metadata. Key \"default\" is always the run's primary store."New value: +"Map of key-value store alias → metadata. Key \"default\"."Output schema / properties / storages / properties / keyValueStores / properties / default / properties / apifyConsoleUrl / descriptionPrevious value: -"Personalized Apify Console link to the store; present only for Console sessions"New value: +"Personalized Apify Console link to the store; present."Output schema / properties / tip / descriptionPrevious value: -"Advisory guidance RAG Web Browser wrote to its key-value store under the reserved \"TIP\" key"New value: +"Advisory guidance RAG Web Browser wrote to its key-value."Output schema / properties / tip / properties / caveat / descriptionPrevious value: -"Present when this session cannot run the Actor the tip recommends"New value: +"Present when this session cannot run the Actor the tip."Output schema / properties / tip / properties / message / descriptionPrevious value: -"Truncated to 300 characters, with a trailing ellipsis if the Actor's message was longer"New value: +"Truncated to 300 characters, with a trailing ellipsis if."gouda_studios--google-trends-explorergouda_studios--google-trends-explorergouda_studios--google-trends-explorergouda_studios--website-contact-extractor1 field changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchemaRemoved value: -{
- "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
- "properties": {
- "addresses": {
- "items": {
- "properties": {
- "city": {
- "type": "string"
- },
- "country": {
- "type": "string"
- },
- "postalCode": {
- "type": [
- "string",
- "null"
- ]
- },
- "region": {
- "type": [
- "null",
- "string"
- ]
- },
- "street": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "charged": {
- "type": "boolean"
- },
- "contactPageUrls": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "domain": {
- "type": "string"
- },
- "emailDetails": {
- "items": {
- "properties": {
- "domainHasMx": {
- "type": "boolean"
- },
- "email": {
- "type": "string"
- },
- "foundOn": {
- "type": "string"
- },
- "isRoleAccount": {
- "type": "boolean"
- },
- "matchesSiteDomain": {
- "type": "boolean"
- },
- "source": {
- "type": "string"
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "emails": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "error": {
- "type": [
- "null",
- "string"
- ]
- },
- "facebook": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "finalUrl": {
- "type": [
- "string",
- "null"
- ]
- },
- "inputUrl": {
- "type": "string"
- },
- "instagram": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "linkedin": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "otherSocials": {
- "properties": {
- "discord": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "github": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "pinterest": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "reddit": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "type": "object"
- },
- "pagesScanned": {
- "type": "number"
- },
- "phoneDetails": {
- "items": {
- "properties": {
- "country": {
- "type": "string"
- },
- "e164": {
- "type": "string"
- },
- "foundOn": {
- "type": "string"
- },
- "international": {
- "type": "string"
- },
- "national": {
- "type": "string"
- },
- "source": {
- "type": "string"
- },
- "type": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": "object"
- },
- "type": "array"
- },
- "phones": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "primaryEmail": {
- "type": [
- "string",
- "null"
- ]
- },
- "primaryPhone": {
- "type": [
- "null",
- "string"
- ]
- },
- "scannedUrls": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "scrapedAt": {
- "type": "string"
- },
- "siteName": {
- "type": [
- "string",
- "null"
- ]
- },
- "status": {
- "type": "string"
- },
- "tiktok": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "x": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "youtube": {
- "items": {
- "type": "string"
- },
- "type": "array"
- }
- },
- "type": "object"
-}gouda_studios--youtube-transcript-extractorgouda_studios--sam-gov-opportunities-feed2 fields changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / contacts / items / properties / email / typePrevious value: -"string"New value: +[
+ "null",
+ "string"
+]Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / solicitationNumber / typePrevious value: -"string"New value: +[
+ "null",
+ "string"
+]gouda_studios--website-contact-extractorabort-actor-runget-actor-runget-dataset-itemsget-key-value-store-recordgouda_studios--gleif-company-lei-lookupgouda_studios--sam-gov-opportunities-feedgouda_studios--sec-edgar-filings-feedgouda_studios--usaspending-awards-searchUS government + SEC data as clean JSON: SAM.gov, USAspending, Grants.gov, Congress, SEC filings.
See who wins US federal contracts and grants (USAspending.gov). $0.02/call via x402.
Pay-per-call US government data: carrier safety, visa sponsors, contracts, employer risk.
US government data as clean JSON for AI agents: SAM.gov contract opportunities, USAspending awards, Grants.gov grants, House STOCK Act trades, and SEC EDGAR filings (Form 4 insider trades, 8-K events, 13F holdings, 13D/G stakes, XBRL fundamentals, 10-K/10-Q sections). 19 read-only tools. Data is as fresh as each source publishes; congressional trades lag up to 45 days and report dollar ranges (House only). Free tier, no card.
Add one secure layer between your agents and this server.
