Skip to main content
Pascal’s hosted services enrich a project’s context and assets. Agents call supported tools with a project, an installed plugin and a credit ceiling. Pascal handles access, pricing, delivery and saved results. The public contract describes what a tool does; private prompts, provider routing and proprietary workflows stay on the host.

​
Discover before spending

The service capabilities document is public and free to read. The MCP server card contains the released tool schemas and side-effect annotations. Neither grants access to a project or permission to spend credits. Connect with the identity described in Connect an AI agent, then call list_pascal_services with the intended pluginId and projectId. This free lookup returns the plugin’s service grants, current prices and available Studio models. Obtain plugin IDs from the project’s installed plugins; knowing an ID does not grant access. Execution requires edit access to the hosted project, an installed curated plugin with the relevant service grant, its required membership and sufficient credits. Autonomous agents must be claimed before spending. The project’s organization wallet is used when the project belongs to an organization; otherwise its authorized personal scope applies. Tool arguments cannot select an arbitrary user or wallet. Current scene-only OAuth connections cannot use the service gateway. Use a Pascal API key authorized for the project or a hosted browser session. Installing a connector or connecting a ChatGPT subscription does not add spending permissions to an OAuth grant.

​
Retrieve site context

pull_site_data retrieves available parcel, zoning, flood, soils, wetlands, elevation and other selected site layers. Each pull uses Pascal credits at the current price returned by list_pascal_services. Coverage depends on the location and requested layer. The result preserves source information, unavailable layers and partial delivery; it is not a guarantee of buildability or a complete survey. Licensed or experimental datasets are not implied by discovery. For example, after checking access with list_pascal_services:
The example assumes Architect is installed and authorized in that project and caps spending at 50 credits. Check the catalog’s current price and choose an approved budget before submitting. Use the actual project ID returned by Pascal. Coordinates can replace the address. The tool returns a retained operationId. While its status is running, call get_site_pull with the same project, plugin and operation ID. Completed and partial results can be reopened without another charge. A failed delivery is refunded. Keep pullKey with the request. After a lost response, retry with exactly the same key and input. A different input with that key is refused; a new key requests another billable pull. Reopening a saved result uses get_site_pull, not another pull.

​
Generate project media

generate_studio_media generates an image, material or video with a model returned by list_pascal_services. Pass its modelId, supported settings, prompt and maxCredits. Optional source references use authorized snapshots or renders from the same project. The gateway calculates the actual price from the model and effective settings. If that price exceeds maxCredits, it refuses the operation before charging. Review the catalog’s pricing unit: a video’s cost can depend on duration and resolution. Save the returned job id and call get_studio_generation to poll or reopen it without another charge. Studio submission is not idempotent: after a lost response, inspect the project’s Studio history before submitting another generation. A new submission can incur another charge.

​
Enrich the scene deliberately

These tools return site context or media references; they do not edit the scene. Use the editor’s normal semantic tools to apply a chosen result, preserving the source and its known limits. Scene validation, saving and project handoff follow the same MCP workflow. Ask Pascal, the hosted MCP endpoint and curated plugin agents share the same service contracts. Local MCP exposes the open-source scene tools by default. A custom host can opt into hosted service tools through the MCP package’s service executor, but must provide an authenticated hosted project. A local scene ID is not a hosted project or an instruction to upload it. Eligible connected ChatGPT subscriptions can fund LLM use when Pascal enables that integration. Site pulls and Studio models continue to use Pascal credits. See Account credits for subscription and top-up behavior.