TabAPI MCP integration for AI agents.
Connect AI agents to TabAPI through 9 structured actions, including find adsense publisher sites, capture url screenshot, and extract url markdown. Review au…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TabAPI integration exposes
The TabAPI Agent App exposes 9 provider-backed actions for data, marketing, and developer tools work. Its current contract lets an authorized agent find domains associated with an adsense publisher id, capture the first viewport of a public url and return a hosted png url, and extract a public web page as markdown. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TabAPI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TabAPI capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_adsense_publisher_sitesREADFind domains associated with an AdSense publisher ID.
INPUTS: pub_id
capture_url_screenshotREVIEWCapture the first viewport of a public URL and return a hosted PNG URL.
INPUTS: url / options
extract_url_markdownREVIEWExtract a public web page as Markdown.
INPUTS: url
get_dns_recordsREADGet DNS records for a domain.
INPUTS: domain / type
get_domain_backlinksREADGet backlink metrics and representative source pages for a domain.
INPUTS: domain
get_domain_rdapREADGet structured RDAP registration data for a domain.
INPUTS: domain
get_domain_trafficREADGet traffic estimates and acquisition channels for a domain.
INPUTS: domain / months
get_domain_whoisREADGet the raw port-43 WHOIS record for a domain.
INPUTS: domain
google_searchREADSearch Google and return normalized result data.
INPUTS: q / country / language / page
INPUT CONTRACTS
Know what the action needs before it runs.
find_adsense_publisher_sites
pub_idREQUIRED- The 16-digit AdSense publisher ID, with or without pub-.
capture_url_screenshot
urlREQUIRED- The public HTTP or HTTPS page URL that TabAPI should capture.
optionsOPTIONAL- Screenshot rendering settings.
extract_url_markdown
urlREQUIRED- The public HTTP or HTTPS page URL that TabAPI should fetch.
get_dns_records
domainREQUIRED- The domain name to inspect, without a URL path.
typeOPTIONAL- The DNS record type, or ALL for every supported type.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Adsense Publisher Sites
Find domains associated with an AdSense publisher ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_adsense_publisher_sitesVerify with Get Dns Records
Get DNS records for a domain. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_dns_recordsSAFETY BOUNDARY
Operate TabAPI with explicit limits
- Authorize TabAPI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned TabAPI data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in TabAPI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the TabAPI task completed successfully.
CONNECTION MODEL
API key
TabAPI API key sent as an Authorization Bearer token. Create or manage keys at https://tabapi.com/settings/apikeys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TabAPI.