Scripted Consultancy
Sign in
Developer access

Connect your operations to the work graph.

Scripted Consultancy is an operational data model. You create organizations, resources, workdays, products, steps, and connections; the simulation uses those records to test how work can be scheduled and improved.

DAG-native

Nodes and directed connections stay in the product graph.

Resource-aware

Use the same resources that power your planning workspace.

Account-scoped

Every key can only reach its own account data.

The mental model

Everything you do becomes structured operational data.

The interface is a convenient way to create and edit database records. The API and MCP server expose the same concepts so your own systems or AI tools can work with the exact same model.

Organization

The ownership and collaboration boundary. Members, API keys, resources, and DAGs belong to an organization.

Resource

A person, machine, vehicle, room, or other capacity that can be assigned to work. Amount and type describe what is available.

Product and DAG

A product is the process being planned. Its DAG contains steps as nodes and dependencies as directed connections.

Workday and timing

Working days, start and end times, step durations, and repeats define when capacity can actually be used.

API record

Each screen action creates or updates a persistent record. Reading the page again reads the current organization data.

Simulation input

The simulation combines the graph, resources, timings, and constraints to evaluate an operational scenario.

How to use the workspace pages

A practical tour of what each page changes and why it matters.

Overview

Start here. See how many organizations you belong to and the current counts for resources, DAGs, and active workdays. Use it to decide what to configure next.

Organizations

Create an organization, invite members, accept invitations, and copy the organization UUID used in API requests. Select the organization you want to work in before editing its data.

Resources

Create the capacity used by your process: people, machines, equipment, or other assets. Keep amounts realistic because availability checks use these values.

DAG

Create a product process, add steps, set durations and types, assign resources, and connect steps. A connection means the source step must precede the destination step.

Workdays

Define when your organization can operate. These hours are combined with step durations and resource availability when planning or simulating work.

Analytics and checks

Review the current graph and run availability, connection, timing, end-node, and workday checks before treating a process as ready for simulation.

API access

Create account-scoped API keys and use the documented routes from Postman, integrations, scripts, or the MCP server. API requests still need the organization UUID.

A reliable simulation workflow

Build from stable foundations, then add complexity one layer at a time.

  1. 1. Select an organization.

    All records and requests must be scoped to the organization you are modeling.

  2. 2. Add resources.

    Describe the capacity that can perform the work and how much is available.

  3. 3. Configure workdays.

    Set the operating window so time calculations have a real calendar.

  4. 4. Build the DAG.

    Create steps, assign durations and resources, then connect dependencies.

  5. 5. Run checks.

    Resolve missing resources, disconnected steps, invalid timings, and end-node issues.

  6. 6. Simulate and compare.

    Change assumptions, run the algorithm, and compare the resulting operational plan.

The MCP server follows this same workflow conversationally: it can create records, inspect the current graph, add dependencies, and prepare a process for checks. It does not bypass organization membership or API-key authorization.

Authentication

Create a key from Account → API access. The full key is displayed once.

Send the key on every external request

Use either header format. The first is easiest to configure in Postman.

X-API-Key: sc_live_your_key
Authorization: ApiKey sc_live_your_key

Keys can be paused or expired. API-key creation, editing, and revocation always require your signed-in Supabase session.

Product and resource endpoints

These are the original Express route names, available under your API base URL.

GET/api/products/get
List the products belonging to the API key's account.
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/products/get"
GET/api/product/info/get?productname=YourProduct
Return a product DAG with its nData nodes and eData connections.
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/product/info/get?productname=YourProduct"
POST/api/product/create
Create an empty product DAG.
{
  "productname": "Custom packaging"
}
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/product/create"
POST/api/product/step/create
Add a node to a product.
{
  "product": "Custom packaging",
  "step": "Cut material"
}
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/product/step/create"
POST/api/product/connection/create
Create a directed edge between two existing nodes.
{
  "product": "Custom packaging",
  "from": "Cut material",
  "to": "Pack order"
}
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/product/connection/create"
POST/api/product/step/resource/add
Assign an existing resource to a product step.
{
  "product": "Custom packaging",
  "step": "Cut material",
  "resource": "Cutter"
}
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/product/step/resource/add"
GET/api/resources
List the resources available to the API key's account.
curl -H "X-API-Key: sc_live_your_key" "http://localhost:8070/api/resources"

Base URL

Local: http://localhost:8070. In production, use the API host configured for your deployment.

The API does not expose your Supabase credentials. Never commit an API key or include it in client-side code or logs.

Manage API keys