Build a portfolio with your AI assistant

What you need before starting

You need an ALTEGO account with access and an assistant that can make HTTP requests. A coding agent, an HTTP tool or a compatible OpenAPI connector can do this. A plain chat without tools cannot call the API just because you paste a key into the conversation.

ALTEGO is in private beta. If you do not have access, join the waitlist first. This guide does not bypass account approval. The integration is a REST API with an OpenAPI schema, not an MCP server.

The authoritative references are the API guide, OpenAPI schema and block and effect catalog. Your assistant should read them before building a page.

Give the assistant the access it needs

Create a personal key in Settings → API. For a draft workflow, choose read and write permissions; add asset upload access if the assistant will upload images or fonts. You can leave publishing permission off and publish yourself in the editor after reviewing the result.

Store the key in the assistant’s secret manager or environment as ALTEGO_API_KEY. It should be sent as a Bearer credential by the HTTP tool, never placed in page content, a public repository or a screenshot. Check that the assistant can use its secret store without printing the value.

A key belongs to its account. It does not grant access to another user’s pages. Choose an expiry that matches the task and revoke the key when it is no longer needed.

Write a brief with real projects and constraints

Give the assistant your display name, an introduction, project titles and exact destination links. Describe each project in your own words, including your role. Mark a workplace as a workplace rather than presenting it as a project you own.

Specify the visual direction and what to avoid. For example: a black-and-white page, a strong heading, three project cards, one music block and a contact link; no flashing animation. Supply approved images or ask the assistant to leave image areas empty. It should not invent clients, metrics or testimonials.

Use https://altego.club/api/v1/guide and https://altego.club/api/v1/openapi.json.
My key is stored as ALTEGO_API_KEY. Do not print it.
Read the block and effect catalog first.
Create a private draft using the project details and images I provide.
Style: black and white, clear project hierarchy, restrained motion.
Do not invent project facts, links, testimonials or assets.
Return the editor link. Ask me before publishing.

Add your actual project details beneath that instruction. The example is a starting brief, not a command that connects an otherwise unsupported assistant.

Create the draft and keep it editable

The assistant creates a page through the API and returns its editor link. The result is a normal ALTEGO document made of blocks, so you can adjust text, frames, styling and effects in the editor. If your editor was already open, reload it to fetch externally created pages.

Ask the assistant to use catalog defaults and existing effect identifiers. Images and fonts must be uploaded before the document refers to them. For layering, the first block in the array is at the back and the last is at the front. The desktop reference canvas is 1280 pixels wide.

For request bodies, scopes and upload limits, use the API reference. The guide and catalog are the source of truth when a saved example differs from the current API.

Review the result as a visitor

Check project descriptions against your brief. Open the links, inspect image crops and use the phone preview. Make sure the most important text and contact action are easy to find. Review motion through a complete cycle rather than only its opening frame.

If the result needs work, give a specific revision: “make the introduction shorter” or “move the contact link below the projects.” Ask the assistant to fetch the latest document and revision before editing and preserve unrelated fields.

Avoid simultaneous manual and assistant edits. A revision conflict means the assistant needs to fetch and reconcile the newer document; it should not blindly overwrite it. After a timeout, the API guide explains how to retry the same operation safely.

Publish only after your review

An editor link is not a published portfolio. When you are satisfied, publish in ALTEGO or explicitly authorise an assistant with publishing permission. Editing a page that is already live can change what visitors see, so a later revision also deserves review.

Use the public share link supplied by the product and check it while signed out. To plan the portfolio’s content before using an assistant, read how to build a visual portfolio. You can also keep the work as a private draft while deciding what to share.