Neon + OpenAI Dots

Build a Neon reader with OpenAI Dots Prepare a grounded database project inventory

Use OpenAI Dots to build a separate read-only Neon assistant with Agent200. Ground the database project inventory in returned source data.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. Neon tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Build a separate database project inventory application with Agent200. Use the runtime’s real schemas and preserve the authenticated user. This is an architecture guide, not a native installation in OpenAI Dots.

Start with one identified project. Preserve returned project, branch, database and operation fields; report missing data and keep the workflow read-only.

Provider reference: Neon API.

Use the provider credential described on the Neon parent page. Keep it in secure configuration and verify the selected tenant or account before reading.

Connector
Neon
Works with
OpenAI Dots · Your own agent code
Authentication
Your Agent200 API key
Tools
5 tools
Model in examples
openai/gpt-5.6-sol

Before you start

  • An Agent200 API key. Create one on the API keys page of the dashboard.
  • Neon enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
  • A model for your agent. The examples use openai/gpt-5.6-sol, through the same Agent200 API key.

Connect Neon to OpenAI Dots

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store the Agent200 API key as an environment variable
    # Keep the key out of your code, prompts and chats.
    export AGENT200_API_KEY="paste-your-key-here"
  2. 2

    Step 2: Inspect the real tool definitions

    Confirm the actual Neon read operations and input schemas in your runtime.

  3. 3

    Step 3: Configure Neon access

    Use the provider-issued credential through the supported Agent200 connection route. Confirm the account scope and inspect the advertised tools before reading.

  4. 4

    Step 4: Build and test the read-only answer

    Prepare the database project inventory only from returned source data. The code example illustrates a sequence, not an SDK installation contract.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "List my Neon projects",
        tools: ["neon"],
      });
    
    console.log(result.output);

Test your connection

Run one request to check everything is wired up.

Ask

Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records.

What should come back

  • The selected project is identified.
  • Only the returned project, branch, database and operation fields are reported.
  • Access gaps and missing context are explicit; no source data is changed.

Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.

Get your API key

Create a key in the Agent200 dashboard. It reaches Neon and every other connector enabled for your project.

Read the SDK docs

Instructions for AI agents

Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Neon to OpenAI Dots.

Agent brief
Goal: connect Neon to OpenAI Dots with Agent200.
Guide: https://www.agent200.com/connectors/neon/framework/openai-dots/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Make sure Neon is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "neon" in the tools. The model decides when a Neon tool is needed; Agent200 executes the call.
5. Check it works with this request: "Read the Neon project I identify and prepare a database project inventory. Name the source and use only project, branch, database and operation fields. State access gaps; do not change records."
   What should come back:
   - The selected project is identified.
   - Only the returned project, branch, database and operation fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.

The code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /connectors/neon/framework/openai-dots.md

Neon tools OpenAI Dots can call

  • List projects

    Read
    neon_list_projects

    Find projects visible to the Neon API key.

  • Read a project

    Read
    neon_get_project

    Retrieve one project by ID.

  • List branches

    Read
    neon_list_branches

    Find branches for an identified project.

  • Read a branch

    Read
    neon_get_branch

    Retrieve one branch by ID.

  • List databases

    Read
    neon_list_databases

    Find databases on the selected branch.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input and the Neon tools.

  2. 02

    The model picks a tool

    The model decides whether a Neon tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It reaches Neon with your Agent200 API key, within the endpoints your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

Permissions at every level. Your project settings decide which services and endpoints the agent may use.

Troubleshooting

The source cannot be read

Check the selected project ID, account scope, read permission and pagination. A project inventory is control-plane metadata, not database row access. Do not expose connection strings or credentials in an agent answer.

FAQ

How do I verify this result?

Compare the named project and returned project, branch, database and operation fields with the source. Treat missing information as missing, not as a fact.

Is this a native product integration?

This describes a separate application built with Agent200 and OpenAI Dots; it does not install a connector into the OpenAI Dots app.

Use Neon with another framework

200 OK

Neon, connected to OpenAI Dots.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)