---
title: Import tools from OpenAPI
description: Create reviewable tool candidates from an API description.
url: "https://docs.actera.tech/docs/guides/importing-tools"
docs_index: /llms.txt
---

> For an index of all documentation, see [/llms.txt](/llms.txt).

Use the Actera CLI to parse an OpenAPI 3 description and create a pending review session.

```bash
actera import -spec ./openapi.yaml
```

You can override the server URL used by the imported operations:

```bash
actera import -spec ./openapi.yaml -base-url https://api.example.com
```

An import does not activate tools. Open the dashboard review screen, inspect each candidate's input schema, risk level, required permissions, and approval setting, then approve the tools you intend to expose.

## Optional metadata

Actera can infer a starting risk and permission configuration. Use `x-actera` in an operation when you need to specify or override it:

```yaml
x-actera:
  risk: destructive
  permissions:
    - project:delete
  confirmation: true
  toolName: deleteProject
  label: Delete project
```

Standard OpenAPI API-key and bearer authentication schemes are detected from the document. OAuth, OpenID Connect, basic authentication, and cookie schemes require manual setup rather than being executed without credentials.

## Sync changes

Run `actera sync` after your backend changes. It discovers an OpenAPI file when one is present, or can read a route-discovery endpoint:

```bash
actera sync --discovery-url https://api.example.com/api/actera-api-routes
```

Use `--dry-run` to inspect candidates without updating the workspace.

---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)