# Getting started with 2TI Native API Architect

> Start with 2TI Native API Architect by checking the release availability on its app page and trying a small, non-sensitive task. This guide explains the first checks to make, how to confirm that your work persists, and what information helps support investigate a problem without exposing private data.

## Before you begin

Check the [app page](/apps/api-architect/) for validated downloads and current pricing terms. A screenshot illustrates a workspace; it does not confirm native support or every feature in your installed build.

## Your first task

Use a local test endpoint first. Inspect the request method, URL and headers before sending. Never paste production keys into a shared collection or include them in an issue report.

## Confirm the result

Review the result in the app, close and reopen the workspace, and check any exported file independently. Stop if the app reports a connection, permission or persistence failure; a preview is not a completed operation.

## Connections and privacy

Only connect services needed for the task. External AI adapters are being prepared per application; do not assume Ollama, Mem0 or Chroma integration from an assistant panel alone. Keep source files and credentials under your control.

## If something goes wrong

Record the app version, operating system, the action you took, the error text and whether you can reproduce it with a test file. Use [app support](/apps/portal?app=api-architect). Remove passwords, license keys, tokens and private content from screenshots and logs.

## Pricing

Commercial plans and prices are being prepared. No paid checkout is available here. Any evaluation terms are shown separately for the applicable release.