API2PDF MCP integration for AI agents.
Connect AI agents to API2PDF through 1 structured actions, including markdown to pdf. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- 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 API2PDF integration exposes
The API2PDF Agent App exposes 1 provider-backed actions for productivity and developer tools work. Its current contract lets an authorized agent convert raw markdown to pdf with api2pdf and return the generated pdf url plus conversion metadata. 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 API2PDF account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real API2PDF capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
markdown_to_pdfREVIEWConvert raw Markdown to PDF with API2PDF and return the generated PDF URL plus conversion metadata.
INPUTS: markdown / fileName / inline / options
INPUT CONTRACTS
Know what the action needs before it runs.
markdown_to_pdf
markdownREQUIRED- The raw Markdown content to convert to PDF.
fileNameOPTIONAL- An optional output PDF file name sent to API2PDF.
inlineOPTIONAL- Whether API2PDF should mark the generated PDF for inline display when possible.
optionsOPTIONAL- Advanced Headless Chrome PDF options forwarded to API2PDF as-is. Use the official API2PDF option keys supported by the /chrome/pdf/markdown endpoint.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Markdown To Pdf
Convert raw Markdown to PDF with API2PDF and return the generated PDF URL plus conversion metadata. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
markdown_to_pdfVerify with Markdown To Pdf
Convert raw Markdown to PDF with API2PDF and return the generated PDF URL plus conversion metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
markdown_to_pdfSAFETY BOUNDARY
Operate API2PDF with explicit limits
- Authorize API2PDF with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned API2PDF 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 API2PDF rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the API2PDF task completed successfully.
CONNECTION MODEL
API key
API2PDF API key sent with the Authorization header. Sign in to the API2PDF portal to get your key: https://portal.api2pdf.com/.
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
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 API2PDF.