Skip to main content
Real questions from Dataleap trainings, answered briefly. Each answer links to the page that goes deeper.
Your costs split into chat costs (building — high at first, zero once the agent is done) and run costs (every execution). For run costs, the levers in order of impact: use event triggers instead of schedules, ask your agent “Would PTC make sense here?” for data-heavy deterministic work, dial the model tier down once the agent is proven, and pre-filter data at the source. Full picture: Credits & usage.
Two things to try. If the workflow is data-heavy and deterministic, ask the agent “Do you use PTC?” — batching the tool calls in a script often fixes both speed and cost. Otherwise, raise its preset one tier and test again — complex workflows sometimes need a bigger context window. The reverse also holds: if it runs well but feels expensive, try a tier lower and check the results stay good.
Two ways. Ad hoc: open the relevant page in your data tool (e.g., Snowflake), copy the URL into the chat, and add a short description of how the data is structured. Durable: create an org-wide skill that defines your metrics once — what each one means and what it’s called in the data — and every agent anyone builds uses the same definitions.
Uploads in the chat are capped at 5 MB. For anything bigger, don’t upload at all — just link the file: connect the app where it already lives (SharePoint, Google Drive, OneDrive, …) and let the agent access it there. That handles files of any size. For reference documents an agent should use permanently, see Add knowledge.
Yes — OCR is a built-in tool, along with web search, transcription of voice memos, image generation, and webhooks. No setup needed.
Agents in your personal space depend on you and your credentials. For workflows others rely on, move them to a team space: they run on team-level credentials (ideally service accounts), everyone can see runs and history, and access survives when people leave — handover is built in.
Share early and visibly: proven agents go into the team space or become templates teammates can clone, and shared standards become skills. Many teams pair this with a short weekly or biweekly champions sync — who’s building what, with clear ownership per workflow.
No. Describe the problem — Dataleap architects the system for you, including sub-agents and PTC where they help. Your job is a clear goal, not a system diagram. The one nudge worth knowing: if a deterministic, data-heavy agent feels slow or expensive, ask it “Do you use PTC?” — it will rethink its structure.

Your first agent

Ready to build? Start here.

Credits & usage

All the cost levers in one place.