Cape API – Keep your sensitive data private while using GPT-4
We’ve built the Cape API so developers can keep sensitive data private while prompting LLMs like GPT-4 and GPT 3.5 Turbo. With Cape, you can easily de-identify sensitive data before sending it to OpenAI. In addition, you can create embeddings from sensitive text and documents and perform vector searches to improve your prompt context all while keeping the data confidential. Developers are using Cape with data like financial statements, legal contracts, and internal/proprietary knowledge that would otherwise be too sensitive to process with the ChatGPT API. You can try CapeChat, our…
In plain words
Cape API is a developer tool that enables the use of large language models like GPT-4 while protecting sensitive information. It de-identifies data such as personal, financial, and health information before sending it to OpenAI, and creates embeddings and performs vector searches on confidential documents. The tool is designed for developers working with sensitive materials like financial statements, legal contracts, and proprietary knowledge that would normally be too risky to process with standard LLM APIs. A free tier and playground are available.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
We’ve built the Cape API so developers can keep sensitive data private while prompting LLMs like GPT-4 and GPT 3.5 Turbo. With Cape, you can easily de-identify sensitive data before sending it to OpenAI. In addition, you can create embeddings from sensitive text and documents and perform vector searches to improve your prompt context all while keeping the data confidential. Developers are using Cape with data like financial statements, legal contracts, and internal/proprietary knowledge that would otherwise be too sensitive to process with the ChatGPT API. You can try CapeChat, our playground for the API at https://chat.capeprivacy.com/ The Cape API is self-serve, and has a free tier. The main features of the API are: De-identification — Redacts sensitive data like PII, PCI, and PHI from your text and documents. Re-identification — Reverts de-identified data back to the original form. Upload documents — Converts sensitive documents to embeddings (supports PDF, Excel, Word, CSV, TXT, PowerPoint, and Markdown). Vector Search — Performs a vector search on your embeddings to augment your prompts with context. To do all this, we work with a number of privacy and security techniques. First of all, we process data within a secure enclave, which is an isolated VM with in-memory encryption. The data remains confidential. No human, including our team at Cape or the underlying cloud provider, can see the data. Secondly, within the secure enclave, Cape de-identifies your data by removing PII, PCI, and PHI before it is processed by OpenAI. As GPT-4 generates and streams back the response tokens, we re-identify the data so it becomes readable again. In addition to de-identification, Cape also has API endpoints for embeddings, vector search, and document uploads, which all operate entirely within the secure enclave (no external calls and no sub-processors). Why did we build this? Developers asked us for help! We've been working at the intersection of privacy and AI since 2017, and with the explosion of interest in LLMs we've had a lot of questions from developers. Privacy and security remain one of the biggest barriers to adopting AI like LLMs, particularly for sensitive data. We’ve spoken with many companies who have been experimenting with ChatGPT or the GPT-4 API and they are extremely excited about the potential, however they find taking an LLM powered feature from PoC to production is a major lift, and it’s uncharted territory for many teams. Developers have questions like: - How do we ensure the privacy of our customer’s data if we’re sending it to OpenAI? - How can we securely feed large bodies of internal, proprietary data into GPT-4? - How can we mitigate hallucinations and bias so that we have higher trust in AI generated text? The features of the Cape API are designed to help solve these problems for developers, and we have a number of early customers using the API in production already. To get started, checkout our docs: https://docs.capeprivacy.com/ View the API reference: https://api.capeprivacy.com/v1/redoc Join the discussion on our Discord: https://discord.gg/nQW7YxUYjh And of course try the CapeChat playground at https://chat.capeprivacy.com/
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, June 2023
the whole month →- NI
Heya HN, I've been working on a reddit-like platform as my primary side project for the last few years. Doing a (very) soft launch today, mainly because I want to use it to encourage discussion of alternatives. How non.io works: 1. Free to browse, paid to interact. 2. Minimum subscription is $2 (though you can choose more). I take $1 to run the servers, everything left gets split evenly between everything you upvote that month. It's a simple model, but I hope it's a better one than the freemium model we've been relying on for the last few years. Fundamentally I feel like any ad-supported…
Commerce · 2023 · non.io
Typefully 2.0▲931Effortlessly publish on Twitter and LinkedIn, now with AI
Growth · 2023 · typefully.com
SlashPage▲760Create websites in seconds to build your first 1K community
Growth · 2023 · slashpage.com
