Building with an agent?
Machine-readable llms.txt, full-text docs, and a public OpenAPI 3.1 spec mean your coding agent can write the integration. Our own apps were built this way.
DeveloperInstant access. One hour to app enablement.
One API. Every holder.
Trusted data feeds. Without the accreditation overhead.
Consented banking and energy data from 100+ sources through one FAPI 2.0 OAuth 2.0 secured REST API. Instant access, first data transfer in under an hour. No accreditation, no scraping, no sales call. Your agent can read the docs itself.
- 10 free credits, no sales call
- 10c per consumer, per app, per month (introductory)
- llms.txt for your coding agent
- Check platform status & known issues
# Any holder, same call. Requires an active
# disclosure consent for the user.
curl https://api.openfeed.au/v1/banking/accounts \
-H "Authorization: DPoP $TOKEN" \
-H "DPoP: $PROOF"
200 OK
{
"version": "V1",
"data": [
{ "accountId": "…", "displayName": "…", "maskedNumber": "…" }
],
"links": {}
}
# Or skip the reading:
# point your coding agent at openfeed.au/llms.txtZero to live trusted data in an hour
Four steps, a copy-paste runbook, and a platform ready to build on from day one. We have spent years implementing CDR compliance so you never have to.
Register an app
Self-serve - start building immediately. 10 free credits on sign-up.
Integrate openfeed data sharing
Deploy an off the shelf Oauth 2.0 library and establish token exchange.
Request onward disclosure
The user picks accounts and confirms on one screen. The heavy consent happens once as they join openfeed.
Fetch data
Banking and energy through the same interface. Normalised, consented, revocable.
Login with openfeed
Add single sign-on with no identity infrastructure to build. Your users authenticate via openfeed while you skip the plumbing and focus on building unique value in your app.
Why build on openfeed
Consent and connectivity belong in the platform, so you just build.
One sprint replaces a quarter of connector work
100+ banking and energy sources through a single OAuth 2.0 secured REST API facade. No per holder or per arrangement plumbing, ever.
Consented, not scraped
Data is sourced via the Australia’s Consumer Data Right and delivered to you under the Privacy Act. Your users never share a password, and your feed never breaks because a bank changed a login page.
Consent your users only suffer once
The consumer’s heavy consent happens once per holder. Your app gets one screen: pick accounts from all sources, confirm. Reused consent lifts activation instead of taxing it.
Batch refresh at least every 6 hours
A predictable, near-real-time baseline that also includes <15 minute live balances. Plenty for budgeting, lending assessment, and switching. If your use case needs faster, tell us.
API at a glance
Everything you need, one interface
Base URL
https://api.openfeed.au/v1Technical
FAPI 2.0 Security ProfileOpenAPI 3.1Pushed Authorization RequestsDPoP
Agents
openfeed.au/llms.txt| Endpoint | Scope | Description |
|---|---|---|
GET /banking/accounts | openfeed-au:data:banking:read | List all banking accounts across connected holders |
GET /banking/accounts/{id} | openfeed-au:data:banking:read | Get banking account detail |
GET /banking/accounts/{id}/balance | openfeed-au:data:banking:read | Get the current banking account balance |
GET /banking/accounts/{id}/transactions | openfeed-au:data:banking:read | List transactions for a banking account |
GET /energy/accounts | openfeed-au:data:energy:read | List all energy accounts across connected holders |
GET /energy/accounts/{id} | openfeed-au:data:energy:read | Get energy account detail |
GET /energy/accounts/{id}/balance | openfeed-au:data:energy:read | Get the current energy account balance |
GET /energy/accounts/{id}/meters | openfeed-au:data:energy:read | List meters for an energy account |
GET /energy/accounts/{id}/meters/{meterId} | openfeed-au:data:energy:read | Get meter detail |
GET /energy/accounts/{id}/meters/{meterId}/usage | openfeed-au:data:energy:read | Get usage data for a meter |
GET /energy/accounts/{id}/meters/{meterId}/der | openfeed-au:data:energy:read | Get DER configuration for a meter |
GET /energy/accounts/{id}/billing | openfeed-au:data:energy:read | Get billing transactions for an energy account |
GET /energy/accounts/{id}/invoices | openfeed-au:data:energy:read | Get invoices for an energy account |
Data endpoints require an active onward disclosure agreement and return 403 disclosure_grant_required otherwise.
The quickstart covers the full flow, or learn more about onward disclosure.
Pricing · Introductory
Cost that scales with usage, not ambition
10cper consumer, per app, per monthIntroductory launch rate
10 free credits to start
Prove value before a dollar or a meeting. No credit card to begin.
Blocks of 100 credits for $10
Credits never expire. Unit cost is modellable to the cent in a board pack.
No platform fees, no tiers, no lock-in
No Contact Sales wall. Stop using any time.
- 20+ YearsThought leadership in data sharing ecosystems
- Every CDR Source100+ Banking and Energy companies available
- Business AssuredSOC2 Type 2 · ISO27001 · ISO27017 · ISO27018 · ASAE 3150
- Best Practice SecuredFAPI 2.0 · PAR · RAR · Grant Management · DPoP · PAN Scrubbing
Be live before lunch
Read the quickstart, or point your coding agent at llms.txt.