canonical: https://jentic.com/apis/dynamics.com/pac # Dynamics PAC The PAC API is a custom Dynamics 365 Business Central integration that exposes read endpoints for the PAC integration resource and for a company within it. It is served through the Business Central gateway and returns data as JSON for a specific environment. The two endpoints are read-only, so the API suits pulling company and integration data out of Business Central rather than writing records back. ## For AI agents Read the PAC integration resource and company data from a Dynamics 365 Business Central environment through two read-only endpoints, returned as JSON. ## Scope Does not handle creating or updating records, invoicing, or payments. Use for reading company and integration data from the PAC Business Central integration only. ## Capabilities - Read the PAC integration resource from Dynamics 365 Business Central - Retrieve company data through the PAC Business Central integration - Pull PAC integration data for a specific Business Central environment as JSON ## Use cases ### Agent-driven integration read An AI agent connected through Jentic can read the PAC integration resource from Dynamics 365 Business Central without opening the client. It calls the read endpoints and receives the integration and company data as JSON, so the agent can surface it to a user or pass it to another step. Example prompt: Call the PAC integration endpoint and return the integration resource it exposes. ### Company data retrieval The PAC API exposes a company endpoint under the integration, so an agent can fetch the data for a specific company in the Business Central environment. This gives a reporting or reconciliation agent a read-only source for the company details the integration surfaces. Example prompt: Fetch the company data from the PAC integration and return it as structured data. ### Integration data sync Because both endpoints are read-only, the PAC API serves as a source for keeping an external system aligned with the integration data in Business Central. A sync agent can periodically read the integration and company resources and upsert them into a downstream store. Example prompt: Read the PAC integration and company resources and upsert the returned data into an external store. ## Key resources - **Integration** — Read the PAC integration resource exposed over the Business Central gateway - **Company** — Read company data through the PAC integration endpoint ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 81 / 100 - AI-Readiness & Agent Experience: 8 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/dynamics.com/pac/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the PAC API by hand means obtaining a bearer token for the Business Central gateway and calling a long URL that embeds the environment and company. Through Jentic you install once, import PAC from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The PAC API exposes only read endpoints, so a rule grants your agent those reads and nothing more. There are no write operations to withhold, because both endpoints only return data. - **Credential handling:** Your PAC bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read company data from the PAC integration', and Jentic returns the matching PAC operation with its input schema so the agent calls it without hunting for the gateway URL. ## Related APIs - **Dynamics 365 Business Central** — The full Business Central API reads and writes the records this PAC integration only reads - **BCGW Export** — BCGW Export is another read-only Business Central gateway API, focused on purchase orders - **Xero Accounting** — Xero exposes company and accounting data as an alternative source outside Dynamics 365 ## FAQ ### What authentication does the PAC API use? The PAC API authenticates with a bearer token on every request, per its OpenAPI spec, which you present in the Authorization header to reach the Business Central gateway. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context. ### Is there a PAC MCP server? You don't need an MCP server to give your agent the PAC API. Jentic connects it directly from the API Directory: import PAC, store your bearer token once, and your agent calls its read endpoints. The operations are discovered on demand, so no extra server's tool definitions are loaded into the agent's context. ### Can I limit what my agent is allowed to do with the PAC API? Yes. The PAC API exposes only read endpoints, so a rule can allow those reads and the agent can do nothing else, and every call it makes is logged. There are no write or delete operations in this API for an agent to reach. ### What does the PAC API return? It returns the PAC integration resource and company data from a Dynamics 365 Business Central environment as JSON through two read-only endpoints. Because it is read-only, it provides data for reporting or integration but does not change records in Business Central. ### What are the rate limits for the PAC API? This OpenAPI spec does not state rate limits; Business Central enforces request throttling per environment and tenant set by Microsoft. Check the Microsoft Dynamics 365 Business Central API documentation for the limits that apply to your tenant. ### How do I read company data with the PAC API through Jentic? Install Jentic One, import PAC from the API Directory, and store your bearer token once. Your agent then searches by intent, for example 'read company data from the PAC integration', and Jentic returns the matching read endpoint with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.