Genipy and the OpenAI API

Reps use it to score and summarize inbound leads, draft outreach for review, summarize email threads before a renewal call, extract fields from order forms and classify win/loss notes. Someone on the team asks their AI for the tool, then clicks Publish.

In ChatGPT, each rep words the request differently and the answer stays in a chat, outside your sales process. A Genipy tool sends the same request every time, from a screen made for the job, and returns the result in the same format for every rep.

Whatever a rep pastes or enters, such as an email thread or an order form, goes to an OpenAI model along with the instructions written into the tool. The model returns a score, a summary, extracted fields or a draft for the rep to check before using it. The tool can also save results in its own database.

No. One OpenAI API key covers the team. A workspace admin enters it once on Genipy’s Integrations page, Genipy confirms with OpenAI that it works, and the admin picks the tools allowed to use it. Genipy gives your AI the setup link.

Only the people you invite by email can open the tool, since every tool is private by default. A Viewer can read what the tool shows, while sending a request to an OpenAI model takes an Editor or an Owner, and the server enforces those roles. If an admin removes the tool’s access to the OpenAI connection, its next calls stop right away.

Not your team. Genipy keeps the key encrypted on its servers, so it stays out of the tool’s code, out of your conversation with your AI and off every screen of the tool. Calls reach OpenAI only through Genipy, which allows only OpenAI operations. Disconnecting the account deletes the stored key.

Not by default. OpenAI’s documentation says data sent to its API is not used to train or improve its models unless you explicitly opt in. Abuse monitoring logs are kept for up to 30 days, longer if the law requires it or to protect its services or others from harm. Zero data retention needs OpenAI’s prior approval.