> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apexgenius.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send the first safe request

> Prove the AI client, ApexGenius account, Salesforce project, and read path before attempting a write.

Your first request should prove the complete read path without changing a record, file, workflow, or deployment.

## Before you ask

Confirm these items in the ApexGenius workspace:

* the intended provider shows as connected and healthy
* the correct Salesforce project is available if the request uses Salesforce
* the AI client has completed browser authorization
* ApexGenius is enabled in the current conversation

## Use the verification prompt

```text theme={"system"}
Which active Flows touch Opportunity?
```

This prompt gives the gateway a narrow discovery task. ApexGenius should find the relevant Salesforce metadata operations, run a read, and return components from the authorized project.

<Steps>
  <Step title="Watch tool discovery">
    The AI client starts with the three public ApexGenius tools and searches for the operation that matches the request.
  </Step>

  <Step title="Confirm the project">
    Check the project name and environment in the response. Stop if the result comes from the wrong production org or sandbox.
  </Step>

  <Step title="Check the evidence">
    A useful answer names the matching Flows or states clearly that none were found. It should not claim a change was made.
  </Step>

  <Step title="Ask one follow-up read">
    Choose a returned Flow and ask ApexGenius to fetch and explain its current source or metadata.
  </Step>
</Steps>

## Other safe first reads

* `List the Salesforce projects available to me.`
* `List the active providers connected to my ApexGenius account.`
* `Describe Opportunity and return only the field names, types, and updateability.`
* `List my n8n workflows without running or changing any of them.`
* `Search Confluence for the deployment runbook without updating any page.`

## What a passing check proves

A successful result proves that the client can reach the ApexGenius endpoint, the OAuth grant maps to your account, the provider is discoverable, and the selected read operation can return authorized data.

It does not prove that write confirmation, downstream automation, or deployment behavior is safe. Test those paths separately with an explicit target, expected effect, rollback, and human review.

<Columns cols={2}>
  <Card title="Understand the request path" icon="route" href="../concepts/how-mcp-works">See each authorization and policy boundary.</Card>
  <Card title="Review every public tool" icon="list-tree" href="../reference/mcp-tools">Read the progressive discovery contract.</Card>
</Columns>