Account & team
Inviting teammates, what each role can do, how trials start and end, and where spending controls live.
Account & team
Your Fiber account is an organization: one credit balance, one set of API keys, one team. We built orgs around two roles and made everything a member needs available to members, so most teams never think about permissions at all.
What each role can do
Two roles exist: Admin and Member.
| Capability | Admin | Member |
|---|---|---|
| Invite and remove members, change roles | Yes | No |
| Billing portal (card, invoices, payment method) | Yes | No |
| Create and revoke API keys | Yes | Yes |
| Manage webhooks | Yes | Yes |
| Edit exclusion lists | Yes | Yes |
| Run searches, enrichments, trackers | Yes | Yes |
| Buy credits, configure auto top-up | Yes | Yes |
Role changes take effect within about a minute.
Inviting teammates
Open Organization in the dashboard sidebar. The Members tab invites by email with a role picker: invite, they accept, they are in. There is no seat limit and no per-seat billing; the org's credits and rate limits are shared.
People can also join without an invite when their email domain matches the one domain your org has claimed: they sign up with their work email and are offered the org. Claim (or change) that domain once, from the Domains tab of the same page; if you need more than one domain, tell us and we will sort it out.
One org per customer is the default: org creation is reserved for Fiber staff, and users who belong to several orgs pick at sign-in.
Your personal settings (name, email, password, multi-factor authentication) live on your profile menu in the sidebar, separate from org settings.
Trials
Two ways to start, both 7 days:
- From the dashboard, with a card. Start a trial on any plan; the card is authorized but charged only when the trial converts. Trial orgs get 500 credits and 100 export rows. Cancel during the trial and nothing is owed; when a canceled period ends, credits zero out and access stops.
- From the API, no card. Verify a work email with a one-time code and get a live API key with 100 credits on the spot: built for agents trying Fiber end-to-end. The Quickstart does it in one command. One trial per company domain, and attaching a card later raises the ceiling to 500. When the 7 days pass without a card, the trial ends. Personal email addresses aren't accepted, the code lasts 10 minutes, and signup usually returns a sandbox key alongside the live one; the Quickstart lists every signup error.
We also nudge you before things run dry: an email fires when your balance drops to 500 credits or fewer, and in-app notifications land in the bell in the sidebar.
Where spending controls live
Credits and plans live on Billing: top-ups, auto top-up with thresholds and caps, plan changes, and per-period usage. The tighter controls are per API key, managed through the API: lifetime credit ceilings, expiration dates, usage resets, and per-key spend views. Once a key reaches its ceiling it can't make more requests, which makes keys the right lever for unsupervised workers and experiments. See API keys for the full set.
API request history
Every call your organization makes to the API is logged for 14 days, with the parameters you sent and how it turned out. When a call fails, you can find it, see exactly what went in, and hand support the request ID instead of reconstructing it from your own logs.
Two ways to read it:
| You want | Use |
|---|---|
| Browse recent calls, newest first, page by page | List requests (up to 100 per page, default 25; follow nextCursor while hasMore is true) |
| Pull everything matching a filter in one call | Download requests (up to 5,000 records per call) |
Both accept the same filters, all optional:
| Filter | Matches |
|---|---|
from | Requests at or after this ISO 8601 timestamp |
to | Requests strictly before this ISO 8601 timestamp |
routePath | An exact route template, e.g. /v1/person/search |
method | An HTTP method, e.g. POST |
statusCode | An exact HTTP status code |
errorCode | A specific error correlation code |
Each record carries id (quote it to support), organizationId,
createdAt, method, routePath, statusCode, durationMs, errorCode
(on failures), and request, the input parameters you sent. Only the request
side is logged; response bodies are not kept. Responses also report
retentionDays.
curl -X POST https://api.fiber.ai/v1/api-requests \
-H "Content-Type: application/json" \
-d '{ "apiKey": "YOUR_API_KEY", "statusCode": 429, "from": "2026-10-01T00:00:00Z" }'When a download matches more than 5,000 requests, it returns 5,000
with truncated: true. Narrow from/to and call again for the rest.
Where each one earns its keep:
- Debugging an error. Got an
errorCodeback? Filter on it to pull the exact request that failed, with its inputs, then send the record'sidto support. - Finding a pattern. Filter on
statusCode(a 429, a 400) and aroutePathto see which calls fail and what they sent. - Auditing usage. Download a day or a week to see which endpoints your workers hit, how often, and how long each call took.
Both operations cost nothing and allow 30 requests per minute each. History older than 14 days is purged, so download anything you need to keep.
Security, SSO, and account deletion
For single sign-on (SSO/SAML), security and compliance reviews (SOC 2, GDPR), or deleting your organization's account and data, email adi@fiber.ai and we'll take it from there.
Operations
| Operation | What it does | Reference |
|---|---|---|
| Send one-time code | Start a cardless API trial by verifying a work email | accountSendOtp |
| Verify one-time code | Exchange the code for trial keys and credits | accountVerifyOtp |
| Attach a card | Add a payment method to a cardless trial, raising its ceiling | cardsAttach |
| List requests | Page through your org's API calls from the last 14 days, with filters | listApiRequests |
| Download requests | Pull up to 5,000 matching API calls in one response | downloadApiRequests |
Trials and request history are free; the operations above cost nothing. Team and role management on this page is dashboard surface. See API keys and Billing for the operations that manage keys and credits.