Skip to main content
Pascal’s hosted services enrich a project’s context and assets. Agents call supported tools with a project, a credit ceiling and, for a plugin’s services, that installed plugin. 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 projectId and, for a plugin’s services, its pluginId. This free lookup returns the service grants, current prices and available Studio models with each model’s supported settings. Obtain plugin IDs from the project’s installed plugins; knowing an ID does not grant access. Execution requires edit access to the hosted project and sufficient credits. A plugin’s service also requires that curated plugin installed with the relevant service grant and its required membership; Studio media without a pluginId needs neither (see Generate project media). 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. A Pascal API key authorized for the project or a hosted browser session can spend once the checks above pass. An OAuth connection (a connected app such as Cursor or ChatGPT) spends only after the person turns on Can spend credits for that connection under Connected apps. Until then, a paid call is refused with spending_not_allowed and a link to that switch; ask the person to turn it on, then call again. Installing a connector or connecting a ChatGPT subscription does not turn it on.

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. Don’t confuse it with the free scene tool get_site, which reads the site already stored in the project: its lot, setbacks, buildable area, street side and ground. pull_site_data fetches new sourced data for an address or coordinates and is billed; get_site_pull reopens a pull you already paid for. 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 a generationKey. Omit pluginId to render as the person in Pascal’s own Studio, with the same edit access and credits as the Studio panel; a plugin’s agent names its plugin. Sources are snapshots or renders from the same project, or a frame view_scene returned ({ "type": "view", "id": "<viewId>" }), which joins the project’s Studio gallery once it is rendered. A source that is gone is refused, never dropped, and so is a setting the model doesn’t support, such as an aspect ratio, duration or resolution it doesn’t offer.

Quote, then render

  1. Look at the scene. On the hosted server, view_scene answers a viewId for the picture it took, alongside the picture:
  2. Ask for a quote. A call without quoteToken charges nothing:
    It answers the model, settings, sources, the exact credits, who pays and a quoteToken (the amount below is illustrative; read the real one from the quote):
  3. Tell the person what it costs and ask. Once they agree, send the same input again with "quoteToken": "v1.…" to submit. The answer is a job with an id.
  4. Call get_studio_generation with that id until it finishes. Pass "includePreview": true to get a finished image back as a picture (WebP, at most 1280 px) beside the job’s details. A video has no preview; give the person its video_url.
When the person said the cost doesn’t matter, skip the quote: pass confirm: false with maxCredits, and the call submits at once. A quote whose input or price changed is refused with quote_changed, and an old one with quote_expired; quote again and tell the person the new price. 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. When Studio cannot make media right now, list_pascal_services lists it as unavailable with no models, and a submission is refused with service_unavailable before any charge. Save the returned job id: get_studio_generation reopens it later without another charge. A failed render is refunded. Keep generationKey, the same for a quote and its submission: after a lost response, the same key and input return the render already created instead of charging again. A different input under that key is refused; a new key is another render. In Pascal’s own chat, the quote appears as a render card the person clicks instead; see Render from the chat.

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. A turn sent through the Pascal API can set a credit cap. Site pulls and Studio media don’t count toward it: each is charged separately, up to its own maxCredits. See Account credits for subscription and top-up behavior.