Writing, translation and organizing notes

Give the task useful context

State the audience, purpose, source facts, length and output format. Paste a short, non-sensitive excerpt. Ask the model to mark missing facts instead of inventing them.

Draft a customer invitation from these facts: fictional bookstore, Saturday 3 pm, reading event. Give a title and a 60-word draft. List any missing facts separately. Do not invent prices or an address.

Work example: a bookstore invitation

1. Start a new chat with <ALBATROSS_MODEL>, the exact text alias allowed for your key. Send: Write a Chinese invitation under 60 characters for the fictional 青禾 bookstore's 春日共读 reading event, Saturday at 3 pm. Remember the event name.
2. Wait for generation to finish, then ask: Translate that invitation into English, keeping the time and event name, under 40 words.
3. Check the date, time and event name yourself. A successful result contains Chinese copy and an English follow-up with the same event details. Copy the approved version into your draft, then export the conversation for your own records.

Adapt it to your work

• Marketing: ask for three tones, choose one, then verify claims before publishing.
• Sales: summarize supplied meeting notes into needs, open questions and next actions; do not invent promises.
• Operations: organize pasted notes into a checklist; this does not require platform administrator access.
• Design: create a brief with subject, palette and exclusions; then follow the image guide for actual generation.

Know what needs another service

• Web search needs the client's own search service and permissions; text success does not verify it.
• Knowledge bases often require embeddings, which this Gateway does not expose. Files may be parsed locally by a client; there is no general Files upload service here.
• Voice and plugins need their own protocols, tools and credentials. They were not validated in this acceptance.

• Use Cherry Studio
• Use Chatbox

Costs and getting help

Albatross Usage and wallet records are the customer bill. Client token counters or price estimates are not your bill; upstream procurement costs are separate. Titles, connection tests and tool continuations may each send paid requests. Stop repeated retries when a request fails.

Invalid Key means checking the Albatross credential. Insufficient quota means checking Albatross balance and limits, not buying a client subscription. For Too Many Requests, wait before retrying; for Gateway Timeout, check Usage before sending again. Both clients displayed these errors in controlled tests; only the invalid-key test reached the local Gateway, with a synthetic key. Quota, rate-limit and timeout responses were simulated without upstream calls.

Contact your Albatross service administrator with the client version, model, time and time zone, error text and request ID if visible. Remove keys, account details and private content from screenshots. Check Usage for keys you can view; ask your organization administrator to check an organization-owned key. Missing records do not mean no charge. Cancelling locally does not guarantee zero upstream work or zero charge.

• Keys, permissions and billing
• Technical error reference