For indie builders

Turn your vibe-coded app into a scholarship product.

Built something with an AI app builder? Our API is two endpoints and plain JSON, so it drops straight in. Give students a reason to come back, and yourself something worth charging for.

Talk to us See Catalog API

How do I add real scholarship data to an app I built with AI?

Ask us for API keys, then have your app fetch the TuitionCovered catalog on the server, store it, and refresh it daily with updated_since. Build search and filters on your copy, and send students to apply with each record's apply_url. The starter prompt below gets an AI app builder most of the way there.

What you can build

A scholarship finder

Search and filters over real, verified scholarships, without building or maintaining a catalog.

Deadline reminders

Email or push reminders before deadlines. Precision is in the data, so you never invent a date.

Personal matches

Ask a few questions, then filter on the eligibility codes to show only what each student can apply for.

A paid tier

Keep search free and charge for alerts, saved lists or application tracking on top.

How it works

Paste this into your AI app builder to get a first version, then make it yours.

1
Get keys
Tell us about your app. We set up your company and you create a key in the portal.
2
Prompt
Paste the starter prompt into your AI builder and set TC_API_KEY on the server.
3
Sync
Your app stores the catalog and fetches only what changed each day.
4
Ship
Launch, watch apply clicks in the portal, and add your paid features.

Starter prompt

Build a scholarship finder.

Data: the TuitionCovered Catalog API (https://api.tuitioncovered.com).
- On the server only, call GET /v1/scholarships with the header
  "Authorization: Bearer" + the TC_API_KEY environment variable.
  Never send the key to the browser.
- Page through results with next_cursor (null on the last page),
  and store every record in the database.
- Once a day, fetch again with updated_since = the last sync time.

UI:
- A search box over title, provider and summary.
- Filters: eligibility.states, eligibility.education_levels,
  eligibility.min_gpa, no_essay, and deadline in the next 30/60/90 days.
- Cards showing title, provider, award.amount and dates.deadline.
  If dates.deadline_precision is "month", show the month only.
- An "Apply" button that opens apply_url in a new tab.
- Treat null fields as "not stated", never as zero or false.

Fields you'll use

Every field is always present in the record, null when the funder doesn't say.

Field	What it's for
title, provider, summary	The card: what it is and who funds it
award.amount, award.amount_type	The headline number, and whether it's fixed, a range or varies
dates.deadline, dates.deadline_precision	Deadline filters and honest reminders
eligibility.states, eligibility.education_levels	The two filters students use most
no_essay	The quick-win filter students ask for
apply_url	Where “Apply” goes; the click is credited to your company

Every field in the API reference

Why TuitionCovered

Two endpoints and one record shape: easy to describe to an AI builder
Every field is always present, so your UI never breaks on a missing key
Apply links are credited to your company, so you can see what you drive
A pilot with real keys before you sign anything

What to use

Vibe-coded apps: common questions

How do I make money from a scholarship app?

That's yours to decide: subscriptions for premium features like alerts and tracking, ads, or your own sponsors. Students looking for scholarships are an audience education and finance brands pay to reach.

Is the API priced for small apps?

It depends on your traffic and how you'll use the data. Tell us what you're building and roughly how many students you expect, and we'll quote. You start on a pilot with real keys before you sign.

Can I search by state through the API?

The API serves the whole active catalog, with incremental sync. Keep a copy in your own database and filter it there by state, level, GPA or anything else in the record.

Can I call the API from the browser?

No. Keys are secret: call the API from your server or a serverless function and serve your own copy to the browser.

All use cases

Tell us what you're building

We'll show you the data for your audience and set you up with the right option.

Talk to us