# Credible > Credible is the AI Analytics Engine. It helps you collect what your data means — definitions, metrics, and institutional knowledge — and write it down as a data model, then delivers that data and its meaning as context to AI agents, dashboards, and products. Built on the open-source modeling language Malloy. ## Product - [AI Analytics Engine](https://www.credibledata.com/ai): Ground LLMs in your governed data over MCP. - [Analytics](https://www.credibledata.com/analytics): Analyze data and get numbers that agree. - [Data Apps](https://www.credibledata.com/data-apps): Build and ship apps and AI features on one governed model, inside your own product. - [Data Modeling](https://www.credibledata.com/data-modeling): Write down what your data means as a semantic data model, and deliver it to every surface. - [Pricing](https://www.credibledata.com/pricing): Metered in tokens, compute time, and bytes served — the units your stack already bills in. ## Company - [About](https://www.credibledata.com/about): The team and mission behind Credible. - [Blog](https://www.credibledata.com/blog): Writing on data modeling, AI, and data infrastructure. - [Case Studies](https://www.credibledata.com/case-studies): How real teams ship trustworthy AI, analytics, and data products on the AI Analytics Engine. - [News](https://www.credibledata.com/news): Company announcements and press releases. - [FAQ](https://www.credibledata.com/faq): Straight answers about what Credible is, how it works, what it connects to, pricing, and security. - [Compare](https://www.credibledata.com/compare): Side-by-side comparisons with the BI tools, semantic layers and AI analysts Credible is evaluated against. ## News - [Credible Data Raises $10 Million to Bring Trusted Business Context to Enterprise AI](https://www.credibledata.com/news/credible-raises-10m-seed): $10M seed from Gradient, SignalFire, and K5 Global to scale the trusted business context engine for enterprise AI, built on open-source Malloy. ## Blog posts - [Version Control for the People Who Own the Numbers](https://www.credibledata.com/blog/posts/version-control-for-the-people-who-own-the-numbers): Code made data models trustworthy and left the business behind. Agents handle the code. Credible handles version control, so everyone ships one data model together. - [Your Data Model Is Part of Your AI System. Evaluate and Optimize It Like One.](https://www.credibledata.com/blog/posts/data-model-evals): Your data model and skills are part of your AI system. The open-source Malloy eval skills test them on your team's questions and let an agent fix what fails. - [Your Vibe-Coded App Just Found Its Serving Layer](https://www.credibledata.com/blog/posts/vibe-coded-data-apps): Vibe-coded data apps stall when it's time to run them in production. Put the app in a Malloy package, and Credible handles login, permissions, hosting, and versions. - [The GraphQL Lesson BI Never Learned](https://www.credibledata.com/blog/posts/graphql-lesson-bi-never-learned): GraphQL let developers get their own data. An agent working from a data model can do the same for business users, and the model says what each number means. - [Curate What Your Agents See](https://www.credibledata.com/blog/posts/curate-what-your-agents-see): An agent with more permission than its caller is a leak. With less, it's a toy. Model the access rule and it inherits exactly theirs. - [The Semantic Layer Is an Interface, Not a Compiler](https://www.credibledata.com/blog/posts/semantic-layer-is-an-interface): Agents didn't make the interface unnecessary. They made it affordable. - [The Looker Migration Guide](https://www.credibledata.com/blog/posts/looker-migration-guide): How to migrate off Looker without rebuilding every dashboard: treat your LookML as the asset, keep the definitions that matter, and prove the numbers still tie out. - [The Omni Migration Guide](https://www.credibledata.com/blog/posts/omni-migration-guide): How to migrate off Omni: trade an app you log into for an engine you build on — you own the model, the skills and the app — and reconcile three layers into one. - [Model the Meaning First. Let It Build the Pipeline.](https://www.credibledata.com/blog/posts/model-meaning-first): The stack writes the pipeline first and the meaning last. Flip the order: write the data model first, and let the engine derive the pipeline from it. - [Inside the AI Analytics Engine](https://www.credibledata.com/blog/posts/inside-the-ai-analytics-engine): Not another data platform: the move from hand-written assembly to compilers to managed runtimes, now in data. One language for "the what"; a runtime for "the how". - [A governed dataset end to end: Claude Code and Malloy on real CVE data](https://www.credibledata.com/blog/posts/claude-code-and-malloy-on-real-cve-data): Every piece from the series — model, lock, ask, ship — applied step by step to real security vulnerability data, with the repo to reproduce it. - [Dashboards Aren't Dead. WYSIWYG Builders Are.](https://www.credibledata.com/blog/posts/dashboards-arent-dead): Drag-and-drop builders compiled clicks into a blob nobody could read. Agents write the app instead -- as source code, against a governed model. - [How an agent turns a question into a trustworthy answer](https://www.credibledata.com/blog/posts/how-an-agent-turns-a-question-into-a-trustworthy-answer): The analysis skills teach an agent the discipline that separates an analyst from a confident guesser — shown on one question, with every check run for real. - [How an agent builds a data model and shows its work](https://www.credibledata.com/blog/posts/how-an-agent-builds-a-semantic-model): The open-source Malloy modeling skills teach an agent to investigate data before it models it, and to flag the decisions the data can't settle. - [The skills and tools that make an agent a data expert](https://www.credibledata.com/blog/posts/open-sourcing-malloy-agents): Malloy Publisher now ships five MCP retrieval tools and thirty agent skills — and the design principles that decide what belongs in a tool versus a skill. - [Tutorial: Use Malloy Publisher to model and analyze data with an agent](https://www.credibledata.com/blog/posts/query-any-data-with-an-agent): A few-minute setup: point Claude or any MCP agent at Malloy Publisher, model your own data with Malloy, and start asking real analytical questions. - [We Open-Sourced the Thing Everyone Else Is Selling](https://www.credibledata.com/blog/posts/open-sourcing-skills): Credible's agent skills and MCP tools are now open source in Malloy Publisher. Why we gave them away, and what we compete on instead. - [Building Atlas: A Data Exploration Platform on Credible and Malloy](https://www.credibledata.com/blog/posts/building-atlas): How we built Atlas, a natural-language data exploration app on Credible and Malloy that turns plain-English questions into governed, interactive charts. - [Charting is Commoditized. Meaning Is the Product.](https://www.credibledata.com/blog/posts/meaning-is-the-product): Charting is commoditized and AI can generate any visualization. The data model — what your data means — is the durable thing analysts and agents share. - [Making Healthcare Data AI-Ready](https://www.credibledata.com/blog/posts/making-healthcare-data-ai-ready): How a governed Malloy data model turns a complex healthcare schema (OMOP) into data that AI agents can query reliably, served to production over MCP. - [The Future of ML Pipelines](https://www.credibledata.com/blog/posts/future-ml-pipelines): Warehouses now run embeddings, classification, and LLM inference natively. The hard part shifts to evaluation, governed logic, and version control. - [Entity Matching with Embeddings](https://www.credibledata.com/blog/posts/entity-matching): Why embedding models beat brittle string-matching for entity resolution, and how to evaluate and iterate on results to ship matching you can trust. - [Rethinking Data Transformation with Malloy](https://www.credibledata.com/blog/posts/malloy-materialization): dbt brought engineering rigor to SQL, but Jinja and YAML complexity compounds. Malloy unifies transformation, modeling, and materialization in one language. ## Case studies - [How VideoAmp shipped AI that answers from its own measurement — or not at all](https://www.credibledata.com/case-studies/videoamp): How VideoAmp shipped client-facing AI reporting that answers only from its own certified measurement — 2,000+ governed definitions, live at Cannes Lions. - [How bars.com built a data product with no data team](https://www.credibledata.com/case-studies/bars-com): How a hospitality company with no data engineers turned a week of manual campaign reporting into answers on demand, built in-house. ## Comparisons - [Credible vs. building it yourself](https://www.credibledata.com/compare/build-it-yourself): Text-to-SQL on your own database works in the demo. Credible adds what production needs: a model of your domain, rules on every query, and a prompt-sized slice. - [Credible vs. the modern data stack](https://www.credibledata.com/compare/modern-data-stack): Four vendors, four bills, and a team to run them. Credible is one engine: describe your domain and it generates pipelines, storage, and serving. No warehouse required. - [Credible vs. Looker](https://www.credibledata.com/compare/looker): Only Looker compiles LookML. Credible makes the model the product: an open language you own, served to every surface. - [Credible vs. Power BI](https://www.credibledata.com/compare/power-bi): Power BI is the most widely deployed BI tool there is. Credible is an engine: one governed model for analytics, data apps, and AI agents, on Microsoft data and more. - [Credible vs. Tableau](https://www.credibledata.com/compare/tableau): Tableau is the standard for visual authoring. Credible builds the chart from a governed model, so getting an answer does not depend on knowing how to build the chart. - [Credible vs. Omni](https://www.credibledata.com/compare/omni): Omni is a well-built BI app, sold as one platform. Credible is an engine: you own the model, the skills and the app, and pay for what you run. - [Credible vs. Sigma](https://www.credibledata.com/compare/sigma): Sigma puts a spreadsheet over your warehouse. Credible is the engine underneath, with no warehouse required, serving one governed model to every surface. - [Credible vs. Lightdash](https://www.credibledata.com/compare/lightdash): Lightdash is open-source BI on top of dbt. Credible opens the layer underneath — Malloy as the language, Malloy Publisher as the server. - [Credible vs. Cube](https://www.credibledata.com/compare/cube): Cube is a mature semantic layer with deep pre-aggregations, and open core like us. We differ on where the model comes from and what travels with it. - [Credible vs. dbt](https://www.credibledata.com/compare/dbt): dbt is the transformation standard. Credible works on the tables it builds, and covers that ground itself in one language with the semantic model. - [Credible vs. Snowflake Cortex](https://www.credibledata.com/compare/snowflake-cortex): Snowflake is the right home for the central data team. Credible is built for the work happening outside it, on every source the business runs on. - [Credible vs. TextQL](https://www.credibledata.com/compare/textql): TextQL is an AI analyst with its ontology in your repository. Credible is the engine behind the agent you already use, serving one governed model over MCP. - [Credible vs. Hex](https://www.credibledata.com/compare/hex): Hex is where analysts work in SQL, Python and R. It consumes a semantic model rather than being one, so it sits alongside Credible more than against it. - [Credible vs. ThoughtSpot](https://www.credibledata.com/compare/thoughtspot): ThoughtSpot pioneered search-driven analytics. Credible answers in words too, but from an open, portable model that serves agents, apps and dashboards. ## Documentation - [Documentation, full text](https://www.credibledata.com/docs/llms-full.txt): Every documentation page below, concatenated into one file. - [Documentation: Get Started with the AI Analytics Engine](https://www.credibledata.com/docs/introduction): Collect the context behind your data, model it once, and deliver it as trusted context to every surface - [Admin API Reference](https://www.credibledata.com/docs/admin-api-reference): Complete Admin API reference for Credible Data's REST endpoints - [Coding API Reference](https://www.credibledata.com/docs/coding-api-reference): Complete Coding API reference for Credible Data's REST endpoints - [Data API Reference](https://www.credibledata.com/docs/data-api-reference): Complete Data API reference for Credible Data's REST endpoints - [Retrieval API Reference](https://www.credibledata.com/docs/retrieval-api-reference): Complete Retrieval API reference for Credible Data's REST endpoints ## Documentation: concepts - [Architecture: How the Engine Serves One Model at Scale](https://www.credibledata.com/docs/concepts/architecture): How Credible serves governed models reliably, at scale, and under load - [The Data Model: What Goes Into One and Why It Matters](https://www.credibledata.com/docs/concepts/data-model): What a data model is, what goes into one, and why it's the foundation of trusted data - [Governance: Access Control as the Path of Least Resistance](https://www.credibledata.com/docs/concepts/governed-platform): How Credible makes governance the path of least resistance - [Malloy vs. SQL: What the Language Adds, and What It Compiles To](https://www.credibledata.com/docs/concepts/malloy-vs-sql): Malloy compiles to SQL and is not a replacement for it — what the language does that SQL cannot, where SQL stays the right tool, and the three error classes Malloy makes unwritable - [Why Malloy: An Open-Source Alternative to SQL and LookML](https://www.credibledata.com/docs/concepts/why-malloy): Malloy is a data modeling language, not YAML or SQL — how it compares to LookML and SQL, and what composable, type-checked, AI-readable models buy you ## Documentation: guides - [MCP Tools](https://www.credibledata.com/docs/how-to/analyzing/ai-assistants-mcp): The Credible consumption MCP server — connecting custom agents, and the tool reference for each endpoint - [Connect your Agent](https://www.credibledata.com/docs/how-to/analyzing/connect-your-llm): Connect Claude, ChatGPT, Gemini, and other MCP-compatible chat clients to your data models - [Dashboards and Notebooks](https://www.credibledata.com/docs/how-to/analyzing/dashboards-and-notebooks): Build dashboards and notebooks as Malloy documents, and add filter controls with givens - [Build Data Apps](https://www.credibledata.com/docs/how-to/analyzing/data-apps): Build and use interactive dashboards and applications shipped with your packages - [Analyze Overview](https://www.credibledata.com/docs/how-to/analyzing/overview): How Credible delivers your data and its meaning as trusted context to every surface - [Connect with Slack](https://www.credibledata.com/docs/how-to/analyzing/slack-integration): Chat with your data directly from Slack using the Credible bot (@CredibleData) - [Analyze Data](https://www.credibledata.com/docs/how-to/analyzing/workspaces): Chat with your data in governed workspaces in the Credible App - [Connect your Coding Agent](https://www.credibledata.com/docs/how-to/developers/connect-coding-agent): Let any coding agent analyze data with your published models - [Embedded Data](https://www.credibledata.com/docs/how-to/developers/embedded-data): Ship CSV and Parquet files inside your packages - [Model Locally with the CLI](https://www.credibledata.com/docs/how-to/developers/local-modeling): One command turns a directory into a local modeling workspace, with a local Publisher serving your model against your real warehouse - [Developer Overview](https://www.credibledata.com/docs/how-to/developers/overview): Local development — the whole engine in your own toolset - [VS Code Extension](https://www.credibledata.com/docs/how-to/developers/vscode-extension): Build data models in VS Code or Cursor with the Credible Extension - [API Access](https://www.credibledata.com/docs/how-to/integrating/apis): Build on the REST APIs - [Migrate from Cube](https://www.credibledata.com/docs/how-to/migrating/cube): Convert your Cube cubes and views into governed Malloy data models - [Migrate from Databricks Metric Views](https://www.credibledata.com/docs/how-to/migrating/databricks): Convert your Unity Catalog metric views into governed Malloy data models - [Migrate from dbt Semantic Layer](https://www.credibledata.com/docs/how-to/migrating/dbt): Convert your dbt semantic models and MetricFlow metrics into governed Malloy data models - [Migrate from Looker](https://www.credibledata.com/docs/how-to/migrating/looker): Convert your LookML views, explores, and models into governed Malloy data models - [Migrate from Omni](https://www.credibledata.com/docs/how-to/migrating/omni): Convert your Omni shared model, topics, and views into governed Malloy data models - [Migration Overview](https://www.credibledata.com/docs/how-to/migrating/overview): Bring the business logic in your existing semantic layers — Looker, Tableau, Power BI, and more — into Credible as governed Malloy data models - [Migrate from Power BI](https://www.credibledata.com/docs/how-to/migrating/power-bi): Convert your Power BI tabular model and DAX measures into governed Malloy data models - [Migrate from Sigma](https://www.credibledata.com/docs/how-to/migrating/sigma): Convert your Sigma data models and workbook logic into governed Malloy data models - [Migrate from Snowflake Semantic Views](https://www.credibledata.com/docs/how-to/migrating/snowflake): Convert your Snowflake semantic views into governed Malloy data models - [Migrate from Tableau](https://www.credibledata.com/docs/how-to/migrating/tableau): Convert your Tableau data sources and calculated fields into governed Malloy data models - [Modeling Overview](https://www.credibledata.com/docs/how-to/modeling/ai-modeling): Build data models with AI agents — in the app or in your IDE - [Connect a Database](https://www.credibledata.com/docs/how-to/modeling/connect-data): Add secure, managed database connections to your environment - [Environments](https://www.credibledata.com/docs/how-to/modeling/environment-overview): The stable, governed foundation for your data - [Row-Level Security and Fine-Grained Access in Malloy](https://www.credibledata.com/docs/how-to/modeling/fine-grained-acls): How to do row-level security, column scope, and source-level access control in Malloy — access rules as two annotations on the sources callers query, enforced on every query - [Git-Backed Modeling: Propose, Review, and Publish Model Changes as a Team](https://www.credibledata.com/docs/how-to/modeling/git-backed-modeling): For teams that share one data model across functions. Anyone proposes a change in plain language, it can be reviewed before it goes live, and approving it publishes it everywhere. - [Build & Publish](https://www.credibledata.com/docs/how-to/modeling/in-app-development): Build, preview, and publish data models with the agent in the Credible App - [Discovery](https://www.credibledata.com/docs/how-to/modeling/metadata-tags): Curate, document, and index your model so people and agents find and understand your data - [Performance & Cost](https://www.credibledata.com/docs/how-to/modeling/persistence): Materialize sources, index dimensions, and pre-aggregate measures for fast, cheap, searchable models - [Publishing](https://www.credibledata.com/docs/how-to/modeling/publishing): Version your package, let Credible prepare it for serving, and serve it to every consumer ## Documentation: administration - [CI/CD: Versioning and Publishing Packages with GitHub Actions](https://www.credibledata.com/docs/platform-admin/cicd): Automated package versioning and publishing with GitHub Actions - [CLI: Script Everything the Credible App Manages](https://www.credibledata.com/docs/platform-admin/cli): Everything the Credible App manages, scriptable from your terminal - [Deployment: Managed Cloud or a Dedicated Cluster](https://www.credibledata.com/docs/platform-admin/deployment): How Credible runs — fully managed in the cloud, or on a dedicated cluster - [Environments and Packages: Best Practices and Release Versioning](https://www.credibledata.com/docs/platform-admin/environments-packages): Common patterns for organizing environments and packages, and for versioning releases - [Users and Groups: Managing Who Is in Your Organization](https://www.credibledata.com/docs/platform-admin/groups-permissions): Manage the users and groups in your organization - [Monitoring: Every User, Every Query, at One Gateway](https://www.credibledata.com/docs/platform-admin/monitoring): What one gateway lets you see — every user, every query, and what the engine does with it - [Permissions: Environments, Packages, Workspaces, and Documents](https://www.credibledata.com/docs/platform-admin/permissions): Who can access what — environments, packages, workspaces, and documents - [Security: Identity, Access Control, and the Audit Trail](https://www.credibledata.com/docs/platform-admin/security): Identity, access control, and the audit trail — enforced at one gateway on every query ## Documentation: reference - [Sign In with Microsoft Entra ID](https://www.credibledata.com/docs/reference/auth/entra-id): Configure Microsoft Entra ID (formerly Azure AD) for single sign-on with Credible - [Setting Up BigQuery](https://www.credibledata.com/docs/reference/connections/bigquery): Create a service account to connect BigQuery to Credible - [BigQuery ML for LLM Classification](https://www.credibledata.com/docs/reference/connections/bigquery-ml): One-time GCP setup to use LLM-based classification via BigQuery ML and Gemini - [Setting Up Databricks](https://www.credibledata.com/docs/reference/connections/databricks): Connect a Databricks SQL warehouse to Credible - [Setting Up DuckLake](https://www.credibledata.com/docs/reference/connections/ducklake): Connect a DuckLake lakehouse (SQL catalog + object storage) to Credible - [Setting Up PostgreSQL](https://www.credibledata.com/docs/reference/connections/postgres): Connect a PostgreSQL database to Credible, including Supabase, and fix the common connection errors ## Documentation: support - [Support](https://www.credibledata.com/docs/community/support): Get help with Credible ## API reference: Admin API - [Delete a group-scoped attribute value](https://www.credibledata.com/docs/admin-api-reference/attributes/delete-a-group-scoped-attribute-value) - [Delete a user-scoped attribute value](https://www.credibledata.com/docs/admin-api-reference/attributes/delete-a-user-scoped-attribute-value): Deletes the attribute value for one user (idempotent). - [Get a trusted attribute and its assigned values](https://www.credibledata.com/docs/admin-api-reference/attributes/get-a-trusted-attribute-and-its-assigned-values): Returns the attribute's declared schema (name + type) and all assigned user/group values. - [List trusted attributes and their assigned values](https://www.credibledata.com/docs/admin-api-reference/attributes/list-trusted-attributes-and-their-assigned-values): Returns every trusted attribute registered for the organization, each with its declared schema (name + type) and all assigned values across user/group/default scopes. Pages over attribute names; the embedded user-values within each attribute are NOT bounded by this pagination. - [Set a group-scoped attribute value](https://www.credibledata.com/docs/admin-api-reference/attributes/set-a-group-scoped-attribute-value): Assigns (creates or replaces) the attribute value for one group, with an optional precedence rank (lower wins for scalar multi-group resolution). - [Set a user-scoped attribute value](https://www.credibledata.com/docs/admin-api-reference/attributes/set-a-user-scoped-attribute-value): Assigns (creates or replaces) the attribute value for one user. The value is type-checked against the attribute's declared type. - [Create a new bookmark](https://www.credibledata.com/docs/admin-api-reference/bookmarks/create-a-new-bookmark): Creates a new bookmark for the current user within the organization. Bookmarks allow users to save references to workspaces, models, and chat conversations. - [Delete a bookmark](https://www.credibledata.com/docs/admin-api-reference/bookmarks/delete-a-bookmark): Deletes a specific bookmark for the current user. This operation cannot be undone. - [Get a specific bookmark](https://www.credibledata.com/docs/admin-api-reference/bookmarks/get-a-specific-bookmark): Retrieves a specific bookmark for the current user by type and object ID. - [List bookmarks for current user](https://www.credibledata.com/docs/admin-api-reference/bookmarks/list-bookmarks-for-current-user): Retrieves all bookmarks for the current user within the specified organization. Optionally filter by bookmark type. - [Create database connection](https://www.credibledata.com/docs/admin-api-reference/connections/create-database-connection): Creates a new database connection for the specified environment with secure credential storage and connection validation. - [Delete database connection](https://www.credibledata.com/docs/admin-api-reference/connections/delete-database-connection): Permanently deletes a database connection and removes all associated credentials. This operation is irreversible. - [Get connection details](https://www.credibledata.com/docs/admin-api-reference/connections/get-connection-details): Retrieves detailed information about a specific database connection including configuration, status, and metadata (credentials are not included for security). - [List database connections](https://www.credibledata.com/docs/admin-api-reference/connections/list-database-connections): Retrieves all database connections configured for the specified environment, including connection metadata, status, and configuration details. - [Update database connection](https://www.credibledata.com/docs/admin-api-reference/connections/update-database-connection): Updates the configuration of an existing database connection, including credentials, settings, and connection parameters. - [Create demo environment](https://www.credibledata.com/docs/admin-api-reference/demo/create-demo-environment): Creates a demo environment with sample data and configurations for testing and demonstration purposes. - [Create self-service organization](https://www.credibledata.com/docs/admin-api-reference/demo/create-self-service-organization): Creates a new organization through self-service registration, allowing users to quickly set up their own organizational environment. - [Create document permission](https://www.credibledata.com/docs/admin-api-reference/documentpermissions/create-document-permission): Creates a new permission assignment for a user or group within the document, granting them specific roles and access levels. Can also be used to request access to the document when the user doesn't have editor or workspace manager permissions. - [Delete document permission](https://www.credibledata.com/docs/admin-api-reference/documentpermissions/delete-document-permission): Removes the permission assignment for a user or group within the document, revoking their access to document resources. - [Get document permission](https://www.credibledata.com/docs/admin-api-reference/documentpermissions/get-document-permission): Retrieves the permission details for a specific user or group within the document, including their role and access level. - [List document permissions](https://www.credibledata.com/docs/admin-api-reference/documentpermissions/list-document-permissions): Retrieves all permission assignments for the specified document, including user and group permissions with their roles and access levels. - [Update document permission](https://www.credibledata.com/docs/admin-api-reference/documentpermissions/update-document-permission): Updates the permission assignment for a user or group within the document, modifying their role and access level. - [Create document](https://www.credibledata.com/docs/admin-api-reference/documents/create-document): Creates a new document within the workspace (the {workspaceName} in the path is the destination), such as a workbook or dashboard. - [Delete document](https://www.credibledata.com/docs/admin-api-reference/documents/delete-document): Permanently deletes a document from the workspace. This operation is irreversible. - [Get document details](https://www.credibledata.com/docs/admin-api-reference/documents/get-document-details): Retrieves detailed information about a specific document including content, metadata, and configuration details. - [List workspace documents](https://www.credibledata.com/docs/admin-api-reference/documents/list-workspace-documents): Retrieves all documents within the specified workspace, including workbooks, dashboards, and other content files. - [Update document](https://www.credibledata.com/docs/admin-api-reference/documents/update-document): Updates the content and metadata of an existing document within the workspace. - [Create environment permission](https://www.credibledata.com/docs/admin-api-reference/environmentpermissions/create-environment-permission): Creates a new permission assignment for a user or group within the environment, granting them specific roles and access levels. Can also be used to request access to the environment when the user doesn't have admin permissions. - [Delete environment permission](https://www.credibledata.com/docs/admin-api-reference/environmentpermissions/delete-environment-permission): Removes the permission assignment for a user or group within the environment, revoking their access to environment resources. - [Get environment permission](https://www.credibledata.com/docs/admin-api-reference/environmentpermissions/get-environment-permission): Retrieves the permission details for a specific user or group within the environment, including their role and access level. - [List environment permissions](https://www.credibledata.com/docs/admin-api-reference/environmentpermissions/list-environment-permissions): Retrieves all permission assignments for the specified environment, including user and group permissions with their roles and access levels. - [Update environment permission](https://www.credibledata.com/docs/admin-api-reference/environmentpermissions/update-environment-permission): Updates the permission assignment for a user or group within the environment, modifying their role and access level. - [Create a new environment](https://www.credibledata.com/docs/admin-api-reference/environments/create-a-new-environment): Creates a new environment within the specified organization. Environments serve as containers for packages and provide a logical grouping for related data models. - [Delete environment](https://www.credibledata.com/docs/admin-api-reference/environments/delete-environment): Permanently deletes a environment and all associated packages, versions, and connections. This operation is irreversible. - [Get environment details](https://www.credibledata.com/docs/admin-api-reference/environments/get-environment-details): Retrieves detailed information about a specific environment including metadata, configuration, and administrative details. - [List environments in organization](https://www.credibledata.com/docs/admin-api-reference/environments/list-environments-in-organization): Retrieves all environments within the specified organization, including metadata such as names, descriptions, creation dates, and replication counts. - [Update environment details](https://www.credibledata.com/docs/admin-api-reference/environments/update-environment-details): Partially updates a environment's details. Only the provided fields will be updated. This operation allows for selective updates without requiring all environment fields. - [Add group members](https://www.credibledata.com/docs/admin-api-reference/groups/add-group-members): Adds new members to a group, including users and nested groups with their specified roles and status. - [Create a new group token](https://www.credibledata.com/docs/admin-api-reference/groups/create-a-new-group-token): Creates a new access token for the specified group. The token secret is only returned in the response to this creation request and cannot be retrieved later. - [Create user group](https://www.credibledata.com/docs/admin-api-reference/groups/create-user-group): Creates a new user group within the organization for organizing users and managing group-based permissions. - [Delete a group token](https://www.credibledata.com/docs/admin-api-reference/groups/delete-a-group-token): Deletes an existing group token. This action is irreversible and will immediately invalidate the token. - [Delete user group](https://www.credibledata.com/docs/admin-api-reference/groups/delete-user-group): Permanently deletes a user group and removes all associated permissions. This operation is irreversible. - [Get group details](https://www.credibledata.com/docs/admin-api-reference/groups/get-group-details): Retrieves detailed information about a specific group including metadata, description, and configuration details. - [Get group members](https://www.credibledata.com/docs/admin-api-reference/groups/get-group-members): Retrieves all members of a group from FGA (Fine-Grained Authorization), including users and nested groups with their membership status and roles. - [List group tokens](https://www.credibledata.com/docs/admin-api-reference/groups/list-group-tokens): Retrieves all access tokens for the specified group. Token secrets are not included in the response for security reasons. - [List organization groups](https://www.credibledata.com/docs/admin-api-reference/groups/list-organization-groups): Retrieves all groups within the specified organization, including metadata such as names, descriptions, and member counts. - [Remove group members](https://www.credibledata.com/docs/admin-api-reference/groups/remove-group-members): Removes members from a group, revoking their group membership and associated permissions. - [Update group configuration](https://www.credibledata.com/docs/admin-api-reference/groups/update-group-configuration): Updates the configuration and metadata of an existing group, including description and other group-level properties. - [Update group member status](https://www.credibledata.com/docs/admin-api-reference/groups/update-group-member-status): Updates a member's status (admin/member) in a group. This operation manages group membership through FGA (Fine-Grained Authorization) and affects the member's permissions within the group. - [Get an index](https://www.credibledata.com/docs/admin-api-reference/indexes/get-an-index) - [List indexes for a version](https://www.credibledata.com/docs/admin-api-reference/indexes/list-indexes-for-a-version): Lists the per-dimension search indexes bound to a package version, most recent first. Each index is the version's serving anchor for one indexed (#(index)-tagged) dimension. The underlying built index is content-addressed and package-scoped (shared across versions that define the same dimension), so it is not exposed here; this returns only the version's bindings. - [Create an organization-creation invite token](https://www.credibledata.com/docs/admin-api-reference/invites/create-an-organization-creation-invite-token): Creates a single organization-creation invite token. The token can be redeemed exactly once via POST /organizations with the X-Invite-Token header set, to create a new organization on the fly. To mint a batch (e.g. for an outreach campaign), call this endpoint once per token — the operation is independent per call so per-invite settings (boundEmail, expiresAt) can vary freely. - [Get a single invite by its token](https://www.credibledata.com/docs/admin-api-reference/invites/get-a-single-invite-by-its-token): Returns invite metadata for the given token (e.g. ABCDE-FGHJK). Used by the signup flow to check redeemability before walking the user through MPA acceptance, and by admin tooling to inspect a specific invite. - [List invite tokens](https://www.credibledata.com/docs/admin-api-reference/invites/list-invite-tokens): Lists previously-created invites along with their consumed state. Each row exposes its raw token (e.g. ABCDE-FGHJK) — tokens are non-secret signup codes, used as the natural id by GET /invites/{token} and DELETE /invites/{token}. - [Revoke an unconsumed invite](https://www.credibledata.com/docs/admin-api-reference/invites/revoke-an-unconsumed-invite): Permanently deletes an unconsumed invite, rendering its token unredeemable. Used to revoke leaked or no-longer-needed invites from an outreach batch. Consumed invites are preserved for audit and cannot be deleted (returns 409). - [Get a materialization](https://www.credibledata.com/docs/admin-api-reference/materializations/get-a-materialization) - [List materializations for a version](https://www.credibledata.com/docs/admin-api-reference/materializations/list-materializations-for-a-version): Lists the per-source materializations bound to a package version (Malloy Persistence v0), most recent first. Each materialization is the lineage anchor for one persist source of the version — identified within the version by its (sourceName, modelFilePath) — and points at the physical table currently serving that source. - [Create organization permission](https://www.credibledata.com/docs/admin-api-reference/organizationpermissions/create-organization-permission): Creates a new permission assignment for a user or group within the organization, granting them specific roles and access levels. Can also be used to request access to the organization when the user doesn't have admin permissions. - [Delete organization permission](https://www.credibledata.com/docs/admin-api-reference/organizationpermissions/delete-organization-permission): Removes the permission assignment for a user or group within the organization, revoking their access to organizational resources. - [Get organization permission](https://www.credibledata.com/docs/admin-api-reference/organizationpermissions/get-organization-permission): Retrieves the permission details for a specific user or group within the organization, including their role and access level. - [List organization permissions](https://www.credibledata.com/docs/admin-api-reference/organizationpermissions/list-organization-permissions): Retrieves all permission assignments for the specified organization, including user and group permissions with their roles and access levels. - [Update organization permission](https://www.credibledata.com/docs/admin-api-reference/organizationpermissions/update-organization-permission): Updates the permission assignment for a user or group within the organization, modifying their role and access level. - [Create a new organization](https://www.credibledata.com/docs/admin-api-reference/organizations/create-a-new-organization): Creates a new organization with the specified configuration. Organizations serve as the top-level container for all resources including environments, packages, workspaces, and user groups. - [Delete an organization](https://www.credibledata.com/docs/admin-api-reference/organizations/delete-an-organization): Permanently deletes an organization and all associated resources including environments, packages, workspaces, and user groups. This operation is irreversible. - [Get organization details](https://www.credibledata.com/docs/admin-api-reference/organizations/get-organization-details): Retrieves detailed information about a specific organization including metadata, configuration, and administrative details. The response includes the current user's permission level (admin, modeler, or member) within the organization. - [Get user within organization context](https://www.credibledata.com/docs/admin-api-reference/organizations/get-user-within-organization-context): Retrieves basic user information for a user within an organization context. This endpoint verifies that both the caller and the target user are members of the specified organization before returning user data. - [List all organizations](https://www.credibledata.com/docs/admin-api-reference/organizations/list-all-organizations): Retrieves a comprehensive list of all organizations accessible to the authenticated user. This endpoint returns organization metadata including names, display names, and timestamps. - [List users in organization](https://www.credibledata.com/docs/admin-api-reference/organizations/list-users-in-organization): Retrieves all users that are members of the specified organization, returning basic user information (userName, email) for each. - [Update organization details](https://www.credibledata.com/docs/admin-api-reference/organizations/update-organization-details): Partially updates an organization's details. Only the provided fields will be updated. This operation allows for selective updates without requiring all organization fields. - [Create package permission](https://www.credibledata.com/docs/admin-api-reference/packagepermissions/create-package-permission): Creates a new permission assignment for a user, group, or workspace within the package, granting them specific roles and access levels. Can also be used to request access to the package when the user doesn't have admin or modeler permissions. - [Delete package permission](https://www.credibledata.com/docs/admin-api-reference/packagepermissions/delete-package-permission): Removes the permission assignment for a user, group, or workspace within the package, revoking their access to package resources. - [Get package permission](https://www.credibledata.com/docs/admin-api-reference/packagepermissions/get-package-permission): Retrieves the permission details for a specific user, group within the package, including their role and access level. - [List package permissions](https://www.credibledata.com/docs/admin-api-reference/packagepermissions/list-package-permissions): Retrieves all permission assignments for the specified package, including user and group permissions with their roles and access levels. - [Update package permission](https://www.credibledata.com/docs/admin-api-reference/packagepermissions/update-package-permission): Updates the permission assignment for a user, group, or workspace within the package, modifying their role and access level. - [Create or update package](https://www.credibledata.com/docs/admin-api-reference/packages/create-or-update-package): Creates a new package or updates an existing one with a new version. This endpoint handles both package metadata and file uploads for package content. - [Delete package](https://www.credibledata.com/docs/admin-api-reference/packages/delete-package): Permanently deletes a package and all associated versions. This operation is irreversible. - [Get package details](https://www.credibledata.com/docs/admin-api-reference/packages/get-package-details): Retrieves detailed information about a specific package including metadata, version information, and configuration details. - [Get package version source](https://www.credibledata.com/docs/admin-api-reference/packages/get-package-version-source): Retrieves the raw package archive (zip) uploaded at publish time for a specific version, defaulting to the package's latest version. - [List accessible packages by organization](https://www.credibledata.com/docs/admin-api-reference/packages/list-accessible-packages-by-organization): Returns a list of package resource identifiers under the given organization that the current user has access to. By default returns only packages the user can share (admin/modeler role). Set onlyShareable=false to include all readable packages (including viewer access). - [List packages in environment](https://www.credibledata.com/docs/admin-api-reference/packages/list-packages-in-environment): Retrieves all packages within the specified environment, including metadata such as names, descriptions, latest versions, and creation timestamps. - [Update package metadata](https://www.credibledata.com/docs/admin-api-reference/packages/update-package-metadata): Updates the metadata and configuration of an existing package, including description, settings, and other package-level properties. - [Create system permission](https://www.credibledata.com/docs/admin-api-reference/permissions/create-system-permission): Creates a system-level permission assignment for administrative functions, granting users elevated privileges across the whole service. - [Create a run (rebuild a version, or a single scoped unit)](https://www.credibledata.com/docs/admin-api-reference/runs/create-a-run-rebuild-a-version-or-a-single-scoped-unit): Starts a run for this package's version identified by versionId. By default (no scope selectors) it is a full run that re-materializes every persist source in the version and rebuilds every indexed dimension it defines — one run driving both unit families through the same two-phase build (tables first, then indexes). It is the on-demand equivalent of the run a publish triggers. - [Get a run](https://www.credibledata.com/docs/admin-api-reference/runs/get-a-run) - [List runs for a package](https://www.credibledata.com/docs/admin-api-reference/runs/list-runs-for-a-package): Lists build/refresh runs for this package, most recent first. A run is a single package-level build event carrying typed units — materialized sources (table units) and built indexes (index units). A run defaults to a full run spanning both families — a publish, an on-demand rebuild, and a scheduled re-materialization all refresh a version's tables and its indexes — but may also be scoped to a single unit (Phase C per-unit dispatch). Runs are version-independent: their artifacts may be shared across versions. - [Perform an action on a run](https://www.credibledata.com/docs/admin-api-reference/runs/perform-an-action-on-a-run): Performs an action on a run. The action is specified via the action query parameter: cancel - Cancels an in-flight (non-terminal) run. - [Create user account](https://www.credibledata.com/docs/admin-api-reference/users/create-user-account): Creates a new user account with profile information and initial configuration. - [Delete user account](https://www.credibledata.com/docs/admin-api-reference/users/delete-user-account): Permanently deletes a user account and removes all associated data. This operation is irreversible. - [Get user details](https://www.credibledata.com/docs/admin-api-reference/users/get-user-details): Retrieves detailed information about a specific user including profile data, tutorial status, and account configuration. - [Update user account](https://www.credibledata.com/docs/admin-api-reference/users/update-user-account): Updates user profile information, tutorial status, and account configuration. - [Get version details](https://www.credibledata.com/docs/admin-api-reference/versions/get-version-details): Retrieves detailed information about a specific package version including metadata, archive status, and creation details. - [List package versions](https://www.credibledata.com/docs/admin-api-reference/versions/list-package-versions): Retrieves all versions of a specific package, including version identifiers, creation timestamps, and archive status information. - [Update version status](https://www.credibledata.com/docs/admin-api-reference/versions/update-version-status): Updates the status of a specific package version, typically used for archiving or unarchiving versions to control their availability. - [Adds package access to a workspace](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/adds-package-access-to-a-workspace) - [Create workspace permission](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/create-workspace-permission): Creates a new permission assignment for a user or group within the workspace, granting them specific roles and access levels. Can also be used to request access to the workspace when the user doesn't have manager permissions. - [Delete workspace permission](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/delete-workspace-permission): Removes the permission assignment for a user or group within the workspace, revoking their access to workspace resources. - [Get workspace permission](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/get-workspace-permission): Retrieves the permission details for a specific user or group within the workspace, including their role and access level. - [List workspace permissions](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/list-workspace-permissions): Retrieves all permission assignments for the specified workspace, including user and group permissions with their roles and access levels. - [Removes package access from a workspace](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/removes-package-access-from-a-workspace) - [Update workspace permission](https://www.credibledata.com/docs/admin-api-reference/workspacepermissions/update-workspace-permission): Updates the permission assignment for a user or group within the workspace, modifying their role and access level. - [Create a new workspace](https://www.credibledata.com/docs/admin-api-reference/workspaces/create-a-new-workspace): Creates a new collaborative workspace within the organization for team-based data modeling and analysis activities. - [Delete workspace](https://www.credibledata.com/docs/admin-api-reference/workspaces/delete-workspace): Permanently deletes a workspace and all its associated data, including packages, permissions, and configuration. This action cannot be undone. - [Get or create personal workspace](https://www.credibledata.com/docs/admin-api-reference/workspaces/get-or-create-personal-workspace): Gets or creates a personal workspace for the current user. This workspace is private and only the user has permissions to read and write documents in it. - [Get workspace details](https://www.credibledata.com/docs/admin-api-reference/workspaces/get-workspace-details): Retrieves detailed information about a specific workspace, including its metadata, associated packages, and configuration settings. - [List workspaces in organization](https://www.credibledata.com/docs/admin-api-reference/workspaces/list-workspaces-in-organization): Retrieves all workspaces within the specified organization, optionally filtered to show only writable workspaces for the current user. - [Update workspace details](https://www.credibledata.com/docs/admin-api-reference/workspaces/update-workspace-details): Partially updates a workspace's details, including description and configuration settings. Only the provided fields will be updated. ## API reference: Data API - [Create a new database connection](https://www.credibledata.com/docs/data-api-reference/connections/create-a-new-database-connection): Creates a new database connection in the specified environment. - [Create SQL source from statement](https://www.credibledata.com/docs/data-api-reference/connections/create-sql-source-from-statement): Creates a Malloy source from a SQL statement using the specified database connection. The SQL statement is executed to generate a source definition that can be used in Malloy models. - [Create SQL source from statement (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/create-sql-source-from-statement-per-package): Creates a Malloy source from a SQL statement using the specified connection, resolved in the context of the named package. - [Create temporary table](https://www.credibledata.com/docs/data-api-reference/connections/create-temporary-table): Creates a temporary table from a SQL statement using the specified database connection. Temporary tables are useful for storing intermediate results during complex queries and data processing workflows. - [Create temporary table (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/create-temporary-table-per-package): Creates a temporary table from a SQL statement using the specified database connection, resolved in the context of the named package. - [Delete a database connection](https://www.credibledata.com/docs/data-api-reference/connections/delete-a-database-connection): Permanently deletes a database connection from the environment. - [Execute SQL query](https://www.credibledata.com/docs/data-api-reference/connections/execute-sql-query): Executes a SQL statement against the specified database connection and returns the results. The results include data, metadata, and execution information. - [Execute SQL query (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/execute-sql-query-per-package): Executes a SQL statement against the specified database connection, resolved in the context of the named package, and returns the results. - [Get connection details](https://www.credibledata.com/docs/data-api-reference/connections/get-connection-details): Retrieves detailed information about a specific database connection within an environment. This includes connection configuration, credentials (if accessible), and metadata. Useful for inspecting connection settings and troubleshooting connectivity issues. - [Get table details from database](https://www.credibledata.com/docs/data-api-reference/connections/get-table-details-from-database): Retrieves a table from the specified database schema. This endpoint is useful for discovering available data sources and exploring the database structure. The schema must exist in the connection for this operation to succeed. The tablePath is the full path to the table, including the schema name. - [Get table details from database (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/get-table-details-from-database-per-package): Retrieves a table from the specified database schema, resolved in the context of the named package. - [List database schemas](https://www.credibledata.com/docs/data-api-reference/connections/list-database-schemas): Retrieves a list of all schemas (databases) available in the specified connection. Each schema includes metadata such as name, description, and whether it's the default schema. This endpoint is useful for exploring the database structure and discovering available data sources. - [List database schemas (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/list-database-schemas-per-package): Retrieves a list of all schemas (databases) available in the specified connection, resolved in the context of the named package. Required for connectionName="duckdb", which is per-package; works for any other connection name as well (resolution falls through to the environment). - [List environment database connections](https://www.credibledata.com/docs/data-api-reference/connections/list-environment-database-connections): Retrieves a list of all database connections configured for the specified environment. Each connection includes its configuration, type, and status information. This endpoint is useful for discovering available data sources within an environment. - [List tables in database](https://www.credibledata.com/docs/data-api-reference/connections/list-tables-in-database): Retrieves a list of all tables and views available in the specified database schema. This endpoint is useful for discovering available data sources and exploring the database structure. The schema must exist in the connection for this operation to succeed. - [List tables in database (per-package)](https://www.credibledata.com/docs/data-api-reference/connections/list-tables-in-database-per-package): Retrieves a list of all tables and views available in the specified database schema, resolved in the context of the named package. - [Update an existing database connection](https://www.credibledata.com/docs/data-api-reference/connections/update-an-existing-database-connection): Updates the configuration of an existing database connection. - [Test database connection configuration](https://www.credibledata.com/docs/data-api-reference/connectionstest/test-database-connection-configuration): Validates a database connection configuration without adding it to any environment. This endpoint allows you to test connection parameters, credentials, and network connectivity before committing the connection to an environment. Useful for troubleshooting connection issues and validating configurations during setup. - [List embedded databases](https://www.credibledata.com/docs/data-api-reference/databases/list-embedded-databases): Retrieves a list of all embedded databases within the specified package. These are typically DuckDB databases stored as .parquet files that provide local data storage for the package. Each database entry includes metadata about the database structure and content. - [Create a new environment](https://www.credibledata.com/docs/data-api-reference/environments/create-a-new-environment): Creates a new Malloy environment with the specified configuration. An environment serves as a container for packages, connections, and other resources. The environment will be initialized with the provided metadata and can immediately accept packages and connections. - [Delete an environment](https://www.credibledata.com/docs/data-api-reference/environments/delete-an-environment): Permanently deletes an environment and all its associated resources including packages, connections, and metadata. This operation cannot be undone, so use with caution. The environment must exist and be accessible for deletion. - [Get environment details and metadata](https://www.credibledata.com/docs/data-api-reference/environments/get-environment-details-and-metadata): Retrieves detailed information about a specific environment, including its packages, connections, configuration, and metadata. The reload parameter can be used to refresh the environment state from disk before returning the information. - [List all available environments](https://www.credibledata.com/docs/data-api-reference/environments/list-all-available-environments): Retrieves a list of all environments currently hosted on this Malloy Publisher server. Each environment contains metadata about its packages, connections, and configuration. This endpoint is typically used to discover available environments and their basic information. - [Update environment configuration](https://www.credibledata.com/docs/data-api-reference/environments/update-environment-configuration): Updates the configuration and metadata of an existing environment. This allows you to modify environment settings, update the README, change the location, or update other environment-level properties. The environment must exist and be accessible. - [Create a materialization](https://www.credibledata.com/docs/data-api-reference/materializations/create-a-materialization): Creates a materialization and starts building. Behavior depends on the request body (see CreateMaterializationRequest): Orchestrated build — supply buildInstructions. The publisher builds directly into the caller-assigned names derived from the package's already-compiled build plan (read off Package.buildPlan). Returns the materialization already building. Auto-run (standalone, default) — omit buildInstructions; the publisher self-assigns names and runs all phases in one pass. - [Delete a materialization](https://www.credibledata.com/docs/data-api-reference/materializations/delete-a-materialization): Deletes a terminal (MANIFEST_FILE_READY, FAILED, or CANCELLED) materialization record. By default this removes the publisher's record only; the caller owns table GC. Set dropTables=true to also drop the physical tables this run produced (from the materialization's manifest) as a best-effort cleanup. - [Get a specific materialization](https://www.credibledata.com/docs/data-api-reference/materializations/get-a-specific-materialization) - [List materializations for a package](https://www.credibledata.com/docs/data-api-reference/materializations/list-materializations-for-a-package): Returns the materialization history for the package, ordered by most recent first. - [Perform an action on a materialization](https://www.credibledata.com/docs/data-api-reference/materializations/perform-an-action-on-a-materialization): Performs an action on a materialization. The action is specified via the action query parameter: stop - Cancels a PENDING or building materialization. Returns 200. - [Compile Malloy source code](https://www.credibledata.com/docs/data-api-reference/models/compile-malloy-source-code): Compiles Malloy source code in the context of a specific model file. The submitted source is appended to the full model content, giving it access to all sources, imports, and queries defined in the model. Relative imports resolve correctly against sibling model files. Returns compilation status and any problems (errors or warnings) found. - [Execute Malloy query](https://www.credibledata.com/docs/data-api-reference/models/execute-malloy-query): Executes a Malloy query against a model and returns the results. The query can be specified as a raw Malloy query string or by referencing a named query within the model. This endpoint supports both ad-hoc queries and predefined model queries, making it flexible for various use cases including data exploration, reporting, and application integration. - [Get compiled Malloy model](https://www.credibledata.com/docs/data-api-reference/models/get-compiled-malloy-model): Retrieves a compiled Malloy model with its source information, queries, and metadata. The model is compiled using the specified version of the Malloy compiler. This endpoint provides access to the model's structure, sources, and named queries for use in applications. - [List package models](https://www.credibledata.com/docs/data-api-reference/models/list-package-models): Retrieves a list of all Malloy models within the specified package. Each model entry includes the relative path, package name, and any compilation errors. This endpoint is useful for discovering available models and checking their status. - [Execute a specific notebook cell](https://www.credibledata.com/docs/data-api-reference/notebooks/execute-a-specific-notebook-cell): Executes a specific cell in a Malloy notebook by index. For code cells, this compiles and runs the Malloy code, returning query results and any new sources defined. For markdown cells, this simply returns the cell content. - [Get Malloy notebook cells](https://www.credibledata.com/docs/data-api-reference/notebooks/get-malloy-notebook-cells): Retrieves a Malloy notebook with its raw cell contents (markdown and code). Cell execution should be done separately via the execute-notebook-cell endpoint. - [List package notebooks](https://www.credibledata.com/docs/data-api-reference/notebooks/list-package-notebooks): Retrieves a list of all Malloy notebooks within the specified package. Each notebook entry includes the relative path, package name, and any compilation errors. This endpoint is useful for discovering available notebooks and checking their status. - [Create a new package](https://www.credibledata.com/docs/data-api-reference/packages/create-a-new-package): Creates a new Malloy package within the specified environment. A package serves as a container for models, notebooks, embedded databases, and other resources. The package will be initialized with the provided metadata and can immediately accept content. - [Delete a package](https://www.credibledata.com/docs/data-api-reference/packages/delete-a-package): Permanently deletes a package and all its associated resources including models, notebooks, databases, and metadata. This operation cannot be undone, so use with caution. The package must exist and be accessible for deletion. - [Get package details and metadata](https://www.credibledata.com/docs/data-api-reference/packages/get-package-details-and-metadata): Retrieves detailed information about a specific package, including its models, notebooks, databases, and metadata. The reload parameter can be used to refresh the package state from disk before returning the information. The versionId parameter allows access to specific package versions. - [List environment packages](https://www.credibledata.com/docs/data-api-reference/packages/list-environment-packages): Retrieves a list of all Malloy packages within the specified environment. Each package contains models, notebooks, databases, and other resources. This endpoint is useful for discovering available packages and their basic metadata. - [Update package configuration](https://www.credibledata.com/docs/data-api-reference/packages/update-package-configuration): Updates the configuration and metadata of an existing package. This allows you to modify package settings, update the description, change the location, or update other package-level properties. The package must exist and be accessible. - [List package pages](https://www.credibledata.com/docs/data-api-reference/pages/list-package-pages): Retrieves a list of all static HTML pages (in-package data apps) within the specified package. Each page entry includes the relative path, the package name, a canonical resource URL, and the page title (extracted from the file's tag, falling back to the path). Used by the Publisher SPA to surface a clickable "Pages" section on the package detail view, and by anyone who wants to discover in-package data apps programmatically without scraping the directory. Recursive depth is capped server-side to keep this cheap on large packages. - [Get server status and health information](https://www.credibledata.com/docs/data-api-reference/publisher/get-server-status-and-health-information): Returns the current status of the Malloy Publisher server, including initialization state, available environments, and server timestamp. This endpoint is useful for health checks and monitoring server availability. - [Get watch mode status](https://www.credibledata.com/docs/data-api-reference/watch-mode/get-watch-mode-status): Retrieves the current status of the file watching system. This includes whether watch mode is enabled, which environment is being watched, and the path being monitored. Useful for monitoring the development workflow and ensuring file changes are being detected. - [Start file watching](https://www.credibledata.com/docs/data-api-reference/watch-mode/start-file-watching): Initiates file watching for the specified environment. This enables real-time monitoring of file changes within the environment directory, allowing for automatic reloading and updates during development. Only one environment can be watched at a time. - [Stop file watching](https://www.credibledata.com/docs/data-api-reference/watch-mode/stop-file-watching): Stops the current file watching session. This disables real-time monitoring of file changes and releases system resources. Use this when development is complete or when switching to a different environment. - [Stream package change events (SSE)](https://www.credibledata.com/docs/data-api-reference/watch-mode/stream-package-change-events-sse): Opens a Server-Sent Events (SSE) stream of file-change events for the package, used by in-package HTML data apps (via the publisher.js runtime) to live-reload when their sources are edited. ## API reference: Retrieval API - [Search or enumerate indexed connection entities](https://www.credibledata.com/docs/retrieval-api-reference/retrieval/search-or-enumerate-indexed-connection-entities): Search for (or, with skip_matching, enumerate) connection-scoped entities in the connection index (tables, columns, and modeling suggestions). Results are always grouped by table. Powers the Credible app's connection schema viewer and the MCP search_database_schema / search_modeling_suggestions tools. Package-scoped retrieval has moved to get_context. Results are scoped to what the caller can access (OpenFGA scoped-access checks). - [Search semantic model context](https://www.credibledata.com/docs/retrieval-api-reference/retrieval/search-semantic-model-context): Search across published semantic models. Each search_targets entry picks an entity type (source, dimension, measure, view, or dimensional_value) with optional search_text; omitting search_text returns the most prominent items of that type. Results are sources with matched entities, ranked by relevance and prominence. Use scopes to narrow the search. ## API reference: Coding API - [Get categorized skill set for a manifest](https://www.credibledata.com/docs/coding-api-reference/codeassist/get-categorized-skill-set-for-a-manifest): Used by the Credible VS Code extension; not part of the external integration surface. Returns the skills referenced by a manifest, categorized into auto_discovered and supporting groups. malloy-* skills come from the pinned @malloy-publisher/skills npm package; manifests and everything else come from the agent-skills repo. If version is omitted, the server resolves the agent-skills half via the Flagsmith flag agent_skills_version and falls back to the agent_skills_version pin; publisher_skills_version does the same for the npm half. The two halves version independently, so freezing a bundle means naming both. The response reports whichever each half resolved to. - [Get information about what extension version is supported](https://www.credibledata.com/docs/coding-api-reference/codeassist/get-information-about-what-extension-version-is-supported): Used by the Credible VS Code extension; not part of the external integration surface. The extension calls this before authenticating to learn the minimum supported version, so it is unauthenticated. - [List manifests available in the agent-skills repo](https://www.credibledata.com/docs/coding-api-reference/codeassist/list-manifests-available-in-the-agent-skills-repo): Used by the Credible VS Code extension; not part of the external integration surface. Discovers all manifests present in the pinned version of the agent-skills repo and returns each with its resolved version (the Flagsmith agent_skills_version flag, else the pin). - [Search Credible documentation](https://www.credibledata.com/docs/coding-api-reference/codeassist/search-credible-documentation): Search Credible's documentation and return the most relevant content as plain text. Authenticate with Authorization: Bearer <auth0-jwt> or Authorization: ApiKey <group-access-token>. - [Search Malloy documentation](https://www.credibledata.com/docs/coding-api-reference/codeassist/search-malloy-documentation): Search Credible's packaged Malloy documentation and return a synthesized answer with relevant passages and code snippets. The corpus is global and the same for every caller — no organization/workspace context is used. Authenticate with Authorization: Bearer <auth0-jwt> or Authorization: ApiKey <group-access-token>. A per-IP rate limit may reject sustained excess traffic with 429 when enforcement is enabled. ## Legal - [Privacy Policy](https://www.credibledata.com/privacy) - [Security](https://www.credibledata.com/security) - [Platform Agreement](https://www.credibledata.com/platform-agreement) - [Subprocessors](https://www.credibledata.com/subprocessors)