Build your own app on Rewardata

Power apps you build with Google AI Studio, Lovable, Base44, Bolt, v0, Replit, Cursor or any AI app builder using the Rewardata REST API or hosted MCP server — standardised pay, tax, social-security, benefits, cost-of-living and global-mobility data for 200+ countries, one consistent interface.

Quick start

1. Get an API key

   Sign in and copy your key from your profile. Keys look like rwd_… and are issued to approved accounts. Send it in the X-API-Key header on every /data call. (The catalogue endpoints — /countries, /fields, /categories — are public and need no key.)

2. Call the REST API

   Base URL https://rewardata.com/api/v1. Full reference at /docs.

   # Pay/tax/COLA data for one country + field
   curl "https://rewardata.com/api/v1/data?country=DEU&field=average_annual_wage" \
        -H "X-API-Key: rwd_your_key_here"
   
   # Global-mobility net-to-net (keep an employee whole when relocating)
   curl -X POST "https://rewardata.com/api/v1/mobility/net-to-net" \
        -H "X-API-Key: rwd_your_key_here" -H "Content-Type: application/json" \
        -d '{"home_country":"USA","host_country":"DEU","household":"family_of_4","gross_salary":200000}'

3. Or connect the MCP server

   For AI agents and builders that speak Model Context Protocol (Claude, Cursor, ChatGPT, agent frameworks), point the client at https://www.rewardata.com/mcp with your API key — the model can then query the data as tools, no glue code.

   {
     "mcpServers": {
       "rewardata": {
         "url": "https://www.rewardata.com/mcp",
         "headers": { "Authorization": "Bearer rwd_your_key_here" }
       }
     }
   }

   "X-API-Key" is accepted here too — same key, either header.

🔒 Keep your app private to your own users

AI app builders publish a public website by default. Two things follow, and both matter: your API key must never reach the browser, and you decide who can use the app.

The pattern

A minimal server-side proxy (works in Supabase / Vercel / Netlify / Base44 functions)

// SERVER-SIDE ONLY — never bundled into the browser.
// The browser calls this (e.g. /api/rewardata), not Rewardata directly.
export default async function handler(req, res) {
  // 1) Require YOUR app's login — only your authenticated users pass.
  const user = await getSessionUser(req);          // Supabase / Clerk / Firebase / Base44 auth
  if (!user) return res.status(401).json({ error: "Sign in required" });

  // 2) Call Rewardata with the secret key (from an env var, never shipped to the client).
  const r = await fetch(
    `https://rewardata.com/api/v1/data?country=${req.query.country}&field=${req.query.field}`,
    { headers: { "X-API-Key": process.env.REWARDATA_API_KEY } }
  );
  res.status(r.status).json(await r.json());
}

• Store the key as a secret (env var / secrets manager), not in the repo or front-end.
• Turn on the builder's auth and require login before the app loads.
• Set the deployment to private / members-only where the builder supports it.
• Optional: have your backend pass an end-user id so you can rate-limit per user.

By app builder

In every case the rule is the same — the key lives server-side, the app sits behind your own login. Here's the tool-specific way to do it. (Steps reflect each tool's standard features; check the linked docs for the latest.)

AI app builders (prompt-to-app)

No-code & internal-tool builders

AI coding IDEs & agents

Design & site builders