Data & Storage · Integration
iLEVEL
Add iLEVEL to your product for your customers, and give your AI agents governed access to it.
Embed an iLEVEL integration so your customers can bring their own portfolio monitoring data into your product instead of rebuilding a spreadsheet each reporting cycle. Every firm tracks a different set of metrics, so record and field mapping is configuration per customer rather than code, and a change to their template is a mapping update rather than a release on yours. fastn handles per-customer credentials, pagination, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own holdings and reported metrics into your product, mapped to their fields.
Pull a reporting period's data so your product works from the current figures rather than a stale copy.
Backfill history on onboarding, throttled so a large import does not exhaust a customer's allowance.
Trigger your product when new period data is available so downstream reporting can run.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads reported metrics before answering a question about a position.
An agent compares two periods and summarises what moved.
An agent reacts to new data landing and prepares the next reporting step within governed permissions.
Example prompt
Pull the latest reported metrics for this portfolio and list the holdings that moved most since last quarter.
Set up iLEVEL in 4 steps
- 01Open the iLEVEL connector from your fastn dashboard.
- 02Have each customer authenticate their own iLEVEL account.
- 03Map the holdings, metrics, and fields your product reads, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the iLEVEL integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an iLEVEL integration without building it. Your customers connect their own iLEVEL account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an iLEVEL update is not your on-call problem.
- One integration serves your product and your agents. The same governed iLEVEL connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Power BI
SnowflakeWorks well with
DealCloudOften used alongside
Tools the same teams tend to run next to iLEVEL, across other categories.
Anthropic Claude
OpenAI
Hugging FaceiLEVEL integration FAQ
How do I add an iLEVEL integration to my product?
Enable the iLEVEL connector in your fastn dashboard, then let each customer authenticate their own iLEVEL account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no iLEVEL client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own iLEVEL account?
Yes. Every connection is scoped to the individual customer, so each authorises their own iLEVEL account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this iLEVEL integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads reported metrics before answering a question about a position.
Who maintains the iLEVEL integration?
fastn does. When iLEVEL changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the iLEVEL integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large iLEVEL reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the iLEVEL integration?
A common starting point: read their own holdings and reported metrics into your product, mapped to their fields. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the iLEVEL integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding iLEVEL does not change your per-connector cost. You can start free with 3 connected accounts.
Add iLEVEL to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.