FAQ

No. Single Origin reads metadata (tables, views, columns) and query or job history. Each connection guide grants metadata access only, such as SNOWFLAKE.OBJECT_VIEWER and USAGE_VIEWER on Snowflake or BROWSE on Databricks.

Snowflake, Databricks, BigQuery, Amazon Redshift, open-source Spark, and Trino or Presto. Some features need one engine's data. For example, query profiles, warehouse rollups and scan cost are Snowflake only. See Connect your warehouse.

Single Origin processes your history one day at a time and analyses each new day. Recommendations carry a processing_time: the day they were written for. Over MCP, list_recommendations results are valid for one hour; ask again after that.

Open the job in the web app and read the Why no recommendation card. Common reasons: the job costs too little to save the minimum per day, it ran on too few days to count as recurring, the daily analysis didn't reach it (the costliest jobs go first), or another recommendation already covers it. See Jobs.

It moves to the Ignored tab. Give a reason: Single Origin carries it into the next analysis of the same workload, so it doesn't propose the same thing again. Over MCP, update_recommendation requires a reason for IGNORED and INVALIDATED.

It compares the cost per day of the covered jobs before and after the change, against a control, and reports the saving with a margin. Measurements are frozen at 7, 30 and 90 days. A person confirms what shipped on the Did this work? tab. See Did this work?.

Single Origin saw the change a recommendation asked for, and the cost fell. Only a person can say whether the fall came from this recommendation or from something else that week. Confirm or correct it on the Did this work? tab.

Any client that supports the streamable HTTP transport and lets you set an Authorization header, such as Claude Code and Cursor. See MCP server.

It is https://<company>-api.singleorigin.tech/mcp, where <company> is your company's name as given by Single Origin. If you're not sure of it, write to [email protected].

The header must be Authorization: Bearer <token_id>:<token_secret>, with both values from Account → Access Tokens joined by a colon. Sending only the secret is the most common mistake. Also check that the token hasn't expired.

Yes, through write tools, such as update_recommendation, which sets a recommendation's status and reason. Each change is recorded under your user. MCP clients usually ask you to approve each write call.

Contact [email protected]. Code review is set up per repository. See SQL code review.