Overview
Openlayer is the AI evaluation and observability platform. This connector gives Claude access to your Openlayer workspace so you can check how your AI systems are doing and fix problems without leaving the conversation. Ask Claude to list projects and inference pipelines, check whether a data source is receiving traffic, pull recent traces and sessions, and summarize test results for a commit or a production pipeline. When a test fails, Claude can fetch the rows that caused the failure, along with the judge explanations, and help you work out why. For governance, Claude can summarize workspace rule status, list failing rule results, and show the evidence behind them. Claude can also create and update projects, pipelines, tests, rules, and frameworks, and run evaluations. Write and delete tools always ask before they run. Each connection is scoped to one workspace you pick when you sign in. Requires an Openlayer account.
Tools
create_framework
ChatGPTcreate_inference_pipeline
ChatGPTcreate_presigned_upload_url
ChatGPTpush_commit on the shared remote server, which can't read a directory on your machine. Tar your project directory yourself, then multipart-POST it to the returned url: include every entry of fields as a form field, and add the tar as a file field LAST in the form (required by S3). Then call finalize_commit with the returned storage_uri.create_project
ChatGPTcreate_rule
ChatGPTcreate_test
ChatGPTdelete_rule
ChatGPTdelete_test
ChatGPTupdate_test(test_id, archived=True)` unless the test should truly disappear: archiving hides the test while preserving its result history, and is reversible. Deleting is appropriate for cleaning up a test that was created by mistake.evaluate_data_source
ChatGPTevaluate_test, which runs one test at a time. Useful for backfilling results after adding tests or after late data arrives. Runs asynchronously: the response carries a background-task ID and a status URL. The requested timestamps are aligned to the tests' evaluation-window boundaries during execution, so the window actually evaluated may be slightly wider than the one requested. Unlike evaluate_test, this route takes no overwrite flag -- use evaluate_test` when you need to overwrite existing results for one test.evaluate_test
ChatGPTfetch_data_source_rows
ChatGPTopenlayer_metric_score_* / openlayer_llm_rubric_score_*) alongside the judge's explanation in the matching *_explanation_* column. To go the other way -- from a failing test to the rows that caused it -- use fetch_failed_rows_for_goal`.fetch_data_source_sessions
ChatGPTfetch_failed_rows_for_goal
ChatGPTjudge_scores list of {score_column, score, test_name, explanation}, where explanation` is the judge's written justification, the same text the UI shows in the record detail panel. Rows are selected using a 3-tier filter strategy: 1) Prefer pre-computed rowsBody.columnFilters from the goal result (update measurement names with llmSettingHash if available; invert operators to target failed rows). 2) Otherwise construct aggregate metric filters (latency/cost/tokens).finalize_commit
ChatGPTget_data_source_health
ChatGPTdateLastSampleReceived says the problem is upstream of Openlayer, not in their tests. The volume series come in fixed hourly/daily/weekly/monthly windows computed by the backend -- the route accepts no time range, so an arbitrary window (say, one specific day last week) cannot be requested here. Use fetch_data_source_rows` with timestamp filters for that.get_data_source_row
ChatGPTget_data_source_session
ChatGPTfetch_data_source_sessions`: returns the session's record count, token usage, cost, duration and scores.get_data_source_session_summary
ChatGPTstale` is true when the session has changed since the summary was written.get_data_source_user
ChatGPTget_framework_project_rule_stats
ChatGPTget_rule_result_evidence
ChatGPTget_test_results
ChatGPTget_workspace_rule_stats
ChatGPTlist_commit_test_results
ChatGPTfetch_failed_rows_for_goal` to drill into the failing rows and read the LLM judge's per-row scores and explanations.list_commits
ChatGPTlist_data_source_user_sessions
ChatGPTlist_data_source_users` surfaces a user whose cost or latency stands out, then this shows that user's sessions.list_data_source_users
ChatGPTlist_framework_documents
ChatGPTlist_framework_rules
ChatGPTlist_frameworks
ChatGPTlist_inference_pipeline_test_results
ChatGPTfetch_failed_rows_for_goal` to drill into the failing rows and read the LLM judge's per-row scores and explanations.list_inference_pipelines
ChatGPTlist_projects
ChatGPTlist_rule_results
ChatGPTlist_rule_tags
ChatGPTlist_rules
ChatGPTlist_test_result_sessions
ChatGPTfetch_failed_rows_for_goal, which only reaches row-level failures. A null score does not necessarily mean the session was unscored -- it depends on the data source's backend. ClickHouse-native data sources return only sessions that have a recorded score in the result's evaluation window; other backends return every session in the window, with score` null where the metric had no resolved value.list_tests
ChatGPTlist_workspace_rule_results
ChatGPTlist_workspaces
ChatGPTretrieve_commit
ChatGPTretrieve_framework
ChatGPTretrieve_framework_document
ChatGPTsections_only=True` to get just the section titles (the outline), then fetch the full content only when needed.retrieve_inference_pipeline
ChatGPTretrieve_rule
ChatGPTretrieve_rule_result
ChatGPTretrieve_test
ChatGPTlist_tests deliberately summarizes thresholds to one line to save tokens, so this is the way to see what a test actually asserts -- the full threshold list, and for LLM-rubric tests the evaluation prompt itself. Read this before calling update_test`, so you preserve the fields you don't mean to change.search_openlayer_docs
ChatGPTupdate_data_source_row
ChatGPTrow are written; other columns are left alone. Confirm the target with get_data_source_row` first.update_framework
ChatGPTenabled=True to activate a framework for the workspace (or False to deactivate). For built-in frameworks only enabled, tags, and project_selector` are mutable.update_project
ChatGPTupdate_rule
ChatGPTupdate_rule_result
ChatGPTupdate_test
ChatGPTthresholds replaces the whole list, so read the current value with retrieve_test` and send the full edited list -- not just the entry you changed.add_rule_result_evidence
Claudecreate_framework
Claudecreate_inference_pipeline
Claudecreate_presigned_upload_url
Claudecreate_project
Claudecreate_rule
Claudecreate_test
Claudedelete_rule
Claudedelete_test
Claudeevaluate_data_source
Claudeevaluate_test
Claudefetch_data_source_rows
Claudefetch_data_source_sessions
Claudefetch_failed_rows_for_goal
Claudefinalize_commit
Claudeget_data_source_health
Claudeget_data_source_row
Claudeget_data_source_session
Claudeget_data_source_session_summary
Claudeget_data_source_user
Claudeget_framework_project_rule_stats
Claudeget_rule_result_evidence
Claudeget_test_results
Claudeget_workspace_rule_stats
Claudelist_commit_test_results
Claudelist_commits
Claudelist_data_source_user_sessions
Claudelist_data_source_users
Claudelist_framework_documents
Claudelist_framework_rules
Claudelist_frameworks
Claudelist_inference_pipeline_test_results
Claudelist_inference_pipelines
Claudelist_projects
Claudelist_rule_results
Claudelist_rule_tags
Claudelist_rules
Claudelist_test_result_sessions
Claudelist_tests
Claudelist_workspace_rule_results
Claudelist_workspaces
Clauderetrieve_commit
Clauderetrieve_framework
Clauderetrieve_framework_document
Clauderetrieve_inference_pipeline
Clauderetrieve_rule
Clauderetrieve_rule_result
Clauderetrieve_test
Claudesearch_openlayer_docs
Claudeupdate_data_source_row
Claudeupdate_framework
Claudeupdate_project
Claudeupdate_rule
Claudeupdate_rule_result
Claudeupdate_test
ClaudeCapabilities
Example Prompts
Click any prompt to copy it.
Links
App Stats
110
Tools
3
Prompts
ChatGPT, Claude
Platforms
Category
Technical Knowledge SearchWorks with
Similar Apps
Data refreshed daily






