Put a structured floorplan workflow behind your product.

Start with the workflow, then define the contract

API access is arranged with the INK TO BRICK team for a supported application on a Business subscription. Tell us what provides the floorplan, which project records the application needs, what output the next system accepts and how people will review the result.

• Source: PDF, image, SVG or DXF floorplans and the context you already collect.
• Workflow: create or inspect a project, follow processing state and read the resulting model record.
• Handoff: agree the model, drawing, data or image output that the receiving tool will verify.
• Operations: define application identity, workspace scope, expected volume and support ownership.

Authentication and workspace access

Each supported application receives scoped OAuth onboarding for the intended workspace. INK TO BRICK reviews the application identity and redirect flow before providing integration details. Keep production credentials in the application’s secret store and do not send them in the contact email.

MCP is the faster path for Codex

If the goal is to let Codex read and analyse an existing workspace, use the self-service MCP connection. Use the API conversation when your own product or automated service needs a supported application contract.

What to include in the request

• The application name, owner and the people who will use it.
• A concrete input-to-output example and expected monthly volume.
• Whether the application reads model context, submits floorplans, requests exports or combines those steps.
• The review, audit and deletion requirements around customer floorplans.

Review Business access, read the API planning guide, or browse all workflow guides.