API keys for your own code

Portail v2.5.0 shipped on 2026-10-03 as a minor release focused on api keys for your own code. Paid plans now include API keys. Create one in Settings > Developer API and your own server can reach your Portail account over HTTPS: search what Portail remembers about you, read your connected apps, and act through them, like sending an email from your Gmail or adding an event to your calendar. The API never runs a model, so calls don't spend credits. Every key carries only the permissions you pick, writes need an idempotency key so a retry can't send the same email twice, and each account has a daily cap on connector calls. Full docs, with curl examples, are at portail.cc/developers. The work is recorded here because small releases are still product history. They change how people sign in, read responses, pay for access, share conversations, open files, or trust the system when something goes wrong.

This was more than a quiet maintenance pass. A minor release changes how a visible part of Portail behaves, how a larger workflow is framed, or how a user understands the product. The important part is not only that the feature exists. The important part is that it joins the rest of the system without making the chat harder to use. Portail is useful because context travels with the user. Every larger release has to protect that feeling.

The main changes were direct: new developer api at api.portail.cc/api/v1 for any paid plan: search your memory, list your connected apps, and run their tools from your own server, up to 5 keys per account, created and revoked in settings > developer api. each key gets only the permissions you choose: read memory, read connected apps, or act in them, the api never runs a language model and never spends credits, write calls (sending email, creating events, publishing posts) need an idempotency-key header, so a retried request returns the first result instead of acting twice, limits: 60 requests a minute per key, plus 2,000 connector reads and 100 connector writes a day per account, shared across its keys, keys are managed only from a signed-in browser, stop working if the plan ends, and refuse calls made from a web page, so a key never ends up in page source, new public docs page at portail.cc/developers, in english and russian, and the chat assistant now knows every current settings tab, including connectors, scheduled tasks and developer api. That list is intentionally plain. It names what changed without turning the release into theatre. When a release fixes a build, a redirect, a storage path, or a UI edge case, the value is often that users stop noticing the problem. The archive keeps that invisible work visible enough for future debugging and for anyone checking whether Portail has cared about the details over time.

For this release, the archive points back to the verified commit trail instead of relying on memory. The title, date, and highlights come from the repository history around v2.5.0. That matters because a release log should be boringly checkable. If someone wants to know why a feature appeared, why a page changed, or why a billing rule behaves differently, the public record and the engineering record should not disagree.

This version also fits into the wider Portail contract. One account, one chat history, and one model picker only work if the smaller pieces keep their promises. Authentication has to fail clearly. Billing has to count honestly. Uploads have to arrive in a form models can read. Admin tools have to show the operator what happened instead of hiding it behind a blank screen. v2.5.0 moved that contract forward in its own narrow lane.

The product lesson is also worth naming. Portail grew quickly through chat, admin, billing, Canvas, Omniverse, Agents, and the coding hand-off bridge. Features landed close together, and some releases bundled polish with deeper infrastructure. This post separates the user-facing promise from the implementation noise. It says what the release changed, why that mattered, and where it sits in the product timeline.

The screenshots attached to this entry show the public release record as it now appears on portail.cc. For older releases, this archive was rebuilt from the git history, package version changes, release modal text, and commit subjects. That means the page is honest about its source: it documents the shipped change and preserves the record going forward, even when the exact old production screen cannot be recreated from a single saved image.

The practical result is simple. Someone landing on this page can see the version number, date, release tier, headline, highlights, and a real rendered screenshot of the archive page. Search engines can index the post through the canonical URL, sitemap entry, and structured data. Future releases now have a standard to meet before deploy, so the history should get cleaner from here instead of fuzzier.