The Megido portal

The people of your organization also work with Megido in its portal: they follow the organization's calls and credits, manage its keys and team, ask the Megido chat and give tasks to Megido's agents. The portal's Guide section holds this guide.

Owners and members

Everyone in an organization sees its calls, credits, revealed sites, feedback and tasks, manages their own API keys and chat apps, and may leave it from their account. An owner also invites people, changes their roles and removes them, sets the organization's settings (whether a second factor is required, whether members may connect chat apps), manages everyone's keys and chat apps, acts on any task and sees Activity.

Actions on access ask for a code first, from your authenticator app or from an email: creating a key, connecting a chat app, inviting someone, changing a role, removing or restoring a member, leaving an organization, and turning the second-factor requirement off or allowing chat apps. A suspended organization can be read in the portal but not changed, and the server refuses its calls.

Sections

Section	What it holds
Research	the Megido chat, when your organization has it
Agents	Megido's agents and the organization's tasks, when your organization has them
Overview	the balance, held and available credits, the coverage spent this period, and daily charts of calls, credits and new results
Calls	every call of the organization: tool, status, new results, charge, and the key, chat app, chat or agent's task it came from; a call opens with the estimate it ran on and, for a paid tool, its result; export as CSV
Feedback	the organization's feedback and the Megido team's progress on it
Credits	every change of the balance: what it was for, the amount and the balance after; export as CSV
Revealed sites	the projects revealed to the organization and the profile parts it bought, each with when it lapses
Keys and apps	API keys, to create and revoke, and the chat apps connected by signing in, to revoke
Team	owners only: the members, invitations and the organization's settings
Activity	owners only: who did what in the organization
Guide	this guide

Connect, at the top of the portal, gives the server's address and the setup of each MCP client. Your account holds your second factor, sessions, organizations and password.

The Megido chat

Research is a chat for people without an AI agent of their own. It calls the same tools at the same prices as an MCP client, shows each call as a card beside its messages, and answers in the language of your message.

• It may ask you to choose before paid calls, and presents what the answers say as shortlists and charts.
• When your organization requires an estimate for a tool, the chat shows the price on a card and makes the call only once you confirm it.
• Besides the calls, the chat charges its model's work in credits, by the tokens the model reads and writes. A turn starts only while your available credits are above zero, and it stops at a spending ceiling: the chat then says what it has done, and Continue goes on in a new turn.
• A ring in the message field shows how full the dialog's context is. Compacting the dialog makes later turns cheaper; at the model's limit the chat compacts it on its own.
• A message that tries to extract the corpus, to learn how the service works inside or to name anonymous projects without a reveal, or that is unsafe, is refused before the model reads it.
• Only the person who started a dialog sees it; everyone in the organization sees its calls and spending, under Calls and Credits. A dialog can be renamed and archived; to delete one, write to Megido support.
• When your organization has agents, the chat can put a request that one of Megido's agents answers on a card, and you give the task from that card. News of the task comes back into the dialog. Accepting a result, taking an offer and confirming a price spend credits, so the chat asks you to confirm each on a card.

Tasks in the portal

When your organization has agents, the Agents section lists Megido's agents and the organization's tasks, with a count of the tasks that wait for its people: an offer, an agent's question, a delivered result, a task given through MCP to confirm. How a task moves and what it costs is in "Tasks for Megido's agents"; this is what the portal adds.

• The catalog shows each agent: what to send, what the result holds and leaves out, its price, or the range of an agent priced by estimate, the hours to delivery, the revision rounds included, and whether Megido checks each result before it is delivered.
• Giving a task. The agent's page takes the brief, up to 10,000 characters, files when the agent takes them, and whether the result is accepted on delivery or by you. Before you send it, the page shows the price, your available credits before and after the hold, and the coverage used this period; for an agent priced by estimate, the range of its price and the offers left unanswered this month. A task can also be given from a card in the Megido chat, or through MCP.
• Files. An agent that takes files names the formats, how many and how large. The server reads text (txt, md, csv, tsv), PDF and images (PNG, JPEG, WebP), up to 10 files a task: a text file up to 1 MB, a PDF up to 20 MB, an image up to 5 MB, and the images of a task up to 20 MB together. The agent treats the files as your data, as it treats the brief.
• Email. The person who gave a task gets an email when an offer is ready, the agent asks a question, a result is delivered, a task given through MCP waits for confirmation, the task fails, or the Megido team writes in its thread.
• The task's page shows its status with the actions open to you, the brief with its files, the thread, and every delivered version of the result, each of which you can download as Markdown. Write there to the agent, or to the Megido team about the task. While a result is delivered or being checked, a message goes to the Megido team only: the agent then hears from you through a revision request.
• Who acts. Everyone in the organization sees its tasks with their briefs, files and results. The person who gave a task and the owners act on it. If that person leaves the organization, the task stays with it: the owners act on it, and nobody gets its emails.
• While agents are switched off, the portal takes no revision request, offer or confirmation.