### API Key Authentication Example

Source: https://docs.revenuebase.ai/docs/getting-started/quickstart

This example demonstrates how to authenticate your API requests using your generated API key. Replace 'YOUR_API_KEY' with your actual key.

```APIDOC
## GET /v1/credits

### Description
Check your remaining credit balance.

### Method
GET

### Endpoint
/v1/credits

### Parameters
#### Headers
- **x-key** (string) - Required - Your RevenueBase API key.

### Request Example
```bash
curl -X GET "https://api.revenuebase.ai/v1/credits" \
  -H "x-key: YOUR_API_KEY"
```

### Response
#### Success Response (200)
- **credits** (integer) - The number of remaining credits.
```

--------------------------------

### API Response Example

Source: https://docs.revenuebase.ai/docs/getting-started/quickstart

Example JSON response when checking your credit balance via the API.

```json
{
  "credits": 1000
}
```

--------------------------------

### Example Verification Summary

Source: https://docs.revenuebase.ai/docs/data-features/data-freshness/verification-summaries

This is an example of the revenuebase_contact_verification_summary field, showing details about LinkedIn profile observation and email verification.

```text
Verified by RevenueBase

Experience last observed on LinkedIn on September 7, 2025: Proposal Manager at Metaphase

Profile: linkedin.com/in/jamie-gregory-xxx333

Email last verified on October 15, 2025 via RevenueBase's Email Verification Tool

Next verification scheduled: November 2025

Learn more at https://revenuebase.ai/verified-by-revenuebase
```

--------------------------------

### Query Shared Snowflake Tables

Source: https://docs.revenuebase.ai/docs/data-feeds/overview

Once a share is accepted, you can query the tables directly using SQL. This example shows how to select the first 100 rows from the PER_LATEST table.

```sql
SELECT *
FROM RELEASE.PER_LATEST
LIMIT 100;
```

--------------------------------

### Send API Key with Request

Source: https://docs.revenuebase.ai/api-reference/v2/authentication

All requests require an API key in the `x-key` header. This example shows how to include it in a `curl` request.

```APIDOC
## Send the key with every request

```bash
curl https://api.revenuebase.ai/v2/account/balance \
  -H "x-key: {YOUR_API_KEY}"
```

The key goes in the `x-key` header — not in `Authorization`, not as a query parameter.
```

--------------------------------

### HTTP Error Codes Reference

Source: https://docs.revenuebase.ai/api-reference/v2/rate-limits

A reference guide to HTTP status codes returned by the RevenueBase API, including their causes and recommended fixes.

```APIDOC
## Error codes

| Status                  | Cause                                                 |
| ----------------------- | ----------------------------------------------------- |
| `400 Bad Request`       | Malformed request body or missing required parameters |
| `401 Unauthorized`      | Missing or invalid API key                            |
| `403 Forbidden`         | Key is valid but not authorized for this endpoint     |
| `404 Not Found`         | Endpoint or resource doesn't exist                    |
| `422 Validation Error`  | Request parsed correctly but failed field validation  |
| `429 Too Many Requests` | Rate limit exceeded                                   |
| `500 Server Error`      | Unexpected error on our end                           |

| Fix                                                                                                |
| -------------------------------------------------------------------------------------------------- |
| Check required fields and data types                                                               |
| Verify the `x-key` header is present and the key is correct                                        |
| Check your account tier and key permissions                                                        |
| Check the URL and endpoint version (`/v1/` vs `/v2/`)                                              |
| Fix the fields listed in the `detail` array (see below)                                            |
| Wait for the window to reset; use exponential backoff                                              |
| Retry with backoff; contact [support@revenuebase.ai](mailto:support@revenuebase.ai) if it persists |
```

--------------------------------

### Make First API Call with cURL

Source: https://docs.revenuebase.ai/

Use this cURL command to make your first API call to verify an email and retrieve enriched contact data. Replace 'YOUR_API_KEY' with your actual API key.

```curl
curl -X POST https://api.revenuebase.ai/v1/process-email \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@example.com"}'
```

--------------------------------

### Join internal accounts to RevenueBase companies by domain

Source: https://docs.revenuebase.ai/docs/data-feeds/joining-overview

Match your account list against RevenueBase companies using the domain. Always normalize domains with LOWER() and strip 'www.' prefixes to prevent mismatches. Consider using TRIM() for whitespace.

```sql
SELECT
    your_accounts.account_name,
    co.COMPANY_NAME,
    co.EMPLOYEE_COUNT_MAX,
    co.INDUSTRY_LINKEDIN
FROM your_database.your_schema.accounts your_accounts
JOIN RELEASE.ORG_LATEST co
  ON LOWER(your_accounts.website_domain) = LOWER(co.DOMAIN);
```

--------------------------------

### Resolve an organization name

Source: https://docs.revenuebase.ai/api-reference/v2/company-match-overview

Send an organization name and optionally a location to get back matching canonical records with firmographic data. Use `result_count` to return multiple candidates when a name is ambiguous.

```APIDOC
## POST /v2/organization/resolve

### Description
Resolves an organization name to a canonical RevenueBase record.

### Method
POST

### Endpoint
/v2/organization/resolve

### Parameters
#### Request Body
- **company_name** (string) - Required - The name of the company to resolve.
- **location** (string) - Optional - The location to filter results by.
- **result_count** (integer) - Optional - The number of candidate matches to return.
```

--------------------------------

### Build Prospect List (SQL)

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/person

Use this query to find decision-makers and influencers at mid-size software companies. It filters by job level, function, industry, and employee count, ordering by the last verified email date.

```sql
SELECT
    PER.FIRST_NAME,
    PER.LAST_NAME,
    PER.EMAIL_ADDRESS,
    PER.JOB_TITLE,
    PER.JOB_LEVEL,
    PER.COMPANY_NAME,
    ORG.EMPLOYEE_COUNT_MAX
FROM RELEASE.PER_LATEST AS PER
INNER JOIN RELEASE.ORG_LATEST AS ORG
ON PER.RBID_ORG = ORG.RBID
WHERE JOB_LEVEL IN ('C-Team', 'VP', 'Director')
  AND JOB_FUNCTION IN ('Engineering', 'Sales')
  AND LINKEDIN_INDUSTRY LIKE '%Software%'
  AND EMPLOYEE_COUNT_MAX BETWEEN 100 AND 1000
ORDER BY EMAIL_LAST_VERIFIED_AT DESC
LIMIT 500;
```

--------------------------------

### Check API Credit Balance

Source: https://docs.revenuebase.ai/docs/getting-started/quickstart

Use this curl command to check your available credits by sending your API key in the x-key header. Keep your API key secret and do not commit it to version control.

```bash
curl -X GET "https://api.revenuebase.ai/v1/credits" \
  -H "x-key: YOUR_API_KEY"
```

--------------------------------

### Recent Job Changers (Last 90 Days)

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/historical-experience

Identify individuals who have started a new job in the last 90 days. This query joins historical experience with person data to retrieve contact information and the new role.

```sql
SELECT
    per.FIRST_NAME_PER,
    per.LAST_NAME_PER,
    per.EMAIL_ADDRESS_PER,
    exp.value:job_title AS new_title,
    exp.value:job_org_name AS new_company,
    per.UPDATED_AT_PER AS profile_updated_at
FROM RELEASE.HISTORICAL_EXPERIENCE_LATEST he
JOIN RELEASE.PER_LATEST per ON he.linkedin_url = per.LINKEDIN_URL_PER
, LATERAL FLATTEN(input => he.jobs) job
, LATERAL FLATTEN(input => job.value:experience) exp
WHERE exp.value:job_is_current = TRUE
  AND per.UPDATED_AT_PER >= DATEADD(day, -90, CURRENT_DATE())
  AND per.EMAIL_ADDRESS_PER IS NOT NULL
ORDER BY per.UPDATED_AT_PER DESC;
```

--------------------------------

### Query Prospect List - No Joins Needed

Source: https://docs.revenuebase.ai/docs/data-features/pre-joined-tables/person-organization

Retrieve a list of prospects with specific job levels, industry, employee count, and country. Results are ordered by email verification date.

```sql
SELECT
    FIRST_NAME,
    LAST_NAME,
    EMAIL_ADDRESS,
    JOB_TITLE,
    COMPANY_NAME_ORG,
    LINKEDIN_INDUSTRY_ORG,
    EMPLOYEE_COUNT_MAX_ORG,
    HEADQUARTERS_STATE_NAME_ORG
FROM RELEASE.VELOCITY_BASE_UNLIMITED_LATEST
WHERE JOB_LEVEL IN ('VP', 'Director', 'C-Suite')
  AND LINKEDIN_INDUSTRY_ORG LIKE '%Software%'
  AND EMPLOYEE_COUNT_MAX_ORG BETWEEN 100 AND 1000
  AND HEADQUARTERS_COUNTRY_NAME_ORG = 'United States'
ORDER BY EMAIL_LAST_VERIFIED_AT DESC
LIMIT 500;
```

--------------------------------

### Send API Key with Request

Source: https://docs.revenuebase.ai/api-reference/v2/authentication

Include your API key in the `x-key` header for all API requests. Ensure the header name is exactly `x-key`.

```bash
curl https://api.revenuebase.ai/v2/account/balance \
  -H "x-key: {YOUR_API_KEY}"
```

--------------------------------

### Authenticate a Request with API Key

Source: https://docs.revenuebase.ai/api-reference/overview

Include your API key in the `x-key` header for every request to authenticate your API calls. This is required for all API interactions.

```bash
curl https://api.revenuebase.ai/v1/credits \
  -H "x-key: {YOUR_API_KEY}"
```

--------------------------------

### Include Verification Context for AI Agent Pipelines

Source: https://docs.revenuebase.ai/docs/data-features/data-freshness/data-freshness

Pass verification fields to AI agents for programmatic decisions on record quality and review flagging.

```sql
-- AI agent pipelines: include verification context for programmatic quality decisions
SELECT
  RBID_PER,
  EMAIL_ADDRESS,
  EMAIL_LAST_VERIFIED_AT,
  REVENUEBASE_CONTACT_VERIFICATION_SUMMARY,
  UPDATED_AT
FROM RELEASE.PER_LATEST
WHERE EMAIL_LAST_VERIFIED_AT IS NOT NULL;
```

--------------------------------

### API Key Authentication

Source: https://docs.revenuebase.ai/api-reference/authentication

All API requests must include your API key in the `x-key` header. Obtain your key from the RevenueBase dashboard under Settings -> API Keys.

```APIDOC
## Get Account Balance Example

### Description
This example demonstrates how to fetch your account balance using an API key.

### Method
GET

### Endpoint
https://api.revenuebase.ai/v2/account/balance

### Headers
- **x-key** (string) - Required - Your API key

### Request Example
```bash
curl https://api.revenuebase.ai/v2/account/balance \
  -H "x-key: {YOUR_API_KEY}"
```

### Response
#### Success Response (200)
- **balance** (number) - The current account balance.

#### Response Example
```json
{
  "balance": 1234.56
}
```
```

--------------------------------

### Verify AWS S3 Bucket Access

Source: https://docs.revenuebase.ai/docs/data-feeds/overview

Use the AWS CLI to list objects in your S3 bucket. Ensure you use the `--request-payer requester` flag as the AWS Console does not support it.

```bash
aws s3 ls s3://<your-bucket-alias>/<delivery_date>/  \
  --request-payer requester  \
  --region <target-bucket-region>
```

```bash
aws s3 ls s3://arn:aws:s3:<region>:<account-id>:accesspoint/<access-point-name>/<delivery_date>/  \
  --request-payer requester  \
  --region <target-bucket-region>
```

--------------------------------

### Handle Authentication Errors

Source: https://docs.revenuebase.ai/api-reference/v2/authentication

Understand the error responses for missing or invalid API keys.

```APIDOC
## Handle authentication errors

A missing or invalid key returns `401 Unauthorized`:

```json
{
  "detail": "Invalid or missing API key"
}
```

A valid key that lacks permission for the endpoint returns `403 Forbidden`:

```json
{
  "detail": "Access denied for this resource"
}
```
```

--------------------------------

### Search Organizations by Keyword

Source: https://docs.revenuebase.ai/api-reference/v2/company-match-overview

Use this endpoint to discover organizations matching a keyword, theme, or description, optionally filtered by location. The `keyword` field accepts natural language descriptions of the organization type.

```bash
curl -X POST https://api.revenuebase.ai/v2/organization/discover \
  -H "x-key: {YOUR_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "keyword": "ambulatory care facilities",
    "location": "Texas",
    "result_count": 10
  }'
```

--------------------------------

### Authentication Errors

Source: https://docs.revenuebase.ai/api-reference/authentication

Understand the error responses for missing or invalid API keys.

```APIDOC
## Authentication Error Examples

### Description
This section details the responses you might receive for authentication-related issues.

### Error Responses

#### 401 Unauthorized
Returned when the API key is missing or invalid.

```json
{
  "detail": "Invalid or missing API key"
}
```

#### 403 Forbidden
Returned when a valid API key lacks the necessary permissions for the requested endpoint.

```json
{
  "detail": "Access denied for this resource"
}
```
```

--------------------------------

### Rotate API Key

Source: https://docs.revenuebase.ai/api-reference/overview

Generate a new API key for your account.

```APIDOC
## GET /v1/new-api-key

### Description
Generate a new API key for your account. Note that this will invalidate your current key.

### Method
GET

### Endpoint
/v1/new-api-key

### Request Example
```bash
curl https://api.revenuebase.ai/v1/new-api-key \
  -H "x-key: {YOUR_API_KEY}"
```

### Response
#### Success Response (200)
- **apiKey** (string) - The newly generated API key.
```

--------------------------------

### Download Batch Verification Results

Source: https://docs.revenuebase.ai/api-reference/email-verification-overview

Once a batch job is completed, use this endpoint with the `process_id` to download the verification results. The results are returned in the same format as the real-time verification response.

```curl
curl https://api.revenuebase.ai/v2/jobs/{PROCESS_ID}/download \
  -H "x-key: {YOUR_API_KEY}"
```

--------------------------------

### Check Credit Balance

Source: https://docs.revenuebase.ai/api-reference/overview

Retrieve the current credit balance for your account.

```APIDOC
## GET /v1/credits

### Description
Check your current credit balance.

### Method
GET

### Endpoint
/v1/credits

### Request Example
```bash
curl https://api.revenuebase.ai/v1/credits \
  -H "x-key: {YOUR_API_KEY}"
```

### Response
#### Success Response (200)
- **credits** (integer) - The remaining credit balance.
```

--------------------------------

### Handle Invalid or Missing API Key Error

Source: https://docs.revenuebase.ai/api-reference/v2/authentication

A `401 Unauthorized` response indicates an invalid or missing API key. Verify the `x-key` header name, ensure the key is copied correctly, and check if it has been revoked.

```json
{
  "detail": "Invalid or missing API key"
}
```

--------------------------------

### Historical Experience + Contacts (Recent Job Changers)

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/historical-experience

Retrieve contact information for recent job changers by joining historical experience data with the person table. Filters for current positions and non-null email addresses.

```sql
SELECT
    per.FIRST_NAME_PER,
    per.LAST_NAME_PER,
    per.EMAIL_ADDRESS_PER,
    exp.value:job_title AS new_title,
    exp.value:job_org_name AS new_company,
    per.JOB_TITLE_PER AS current_title_in_feed
FROM RELEASE.HISTORICAL_EXPERIENCE_LATEST he
JOIN RELEASE.PER_LATEST per ON he.linkedin_url = per.LINKEDIN_URL_PER
, LATERAL FLATTEN(input => he.jobs) job
, LATERAL FLATTEN(input => job.value:experience) exp
WHERE exp.value:job_is_current = TRUE
  AND per.EMAIL_ADDRESS_PER IS NOT NULL
ORDER BY per.UPDATED_AT_PER DESC;
```

--------------------------------

### Batch Process Emails

Source: https://docs.revenuebase.ai/api-reference/overview

Verify deliverability and detect risks for a list of email addresses in bulk.

```APIDOC
## POST /v1/batch-process-email

### Description
Process a list of email addresses in bulk to verify deliverability and detect risks.

### Method
POST

### Endpoint
/v1/batch-process-email

### Request Body
- **emails** (array of strings) - Required - A list of email addresses to process.

### Request Example
```json
{
  "emails": [
    "test1@example.com",
    "test2@example.com"
  ]
}
```

### Response
#### Success Response (200)
- **results** (array of objects) - A list of results for each processed email.
  - **email** (string) - The processed email address.
  - **status** (string) - The deliverability status.
  - **role** (string) - Indicates if the email is a role account.
  - **risk_score** (integer) - A score indicating the risk associated with the email.
```

--------------------------------

### Rate Limit Tracking Headers

Source: https://docs.revenuebase.ai/api-reference/v2/rate-limits

Monitor your API usage in real-time using the rate limit headers included in every response.

```APIDOC
## Track usage with response headers

Every response includes rate limit headers:

| Header                  | Description                                | 
| ----------------------- | ------------------------------------------ |
| `X-RateLimit-Limit`     | Max requests allowed in the current window |
| `X-RateLimit-Remaining` | Requests remaining in the current window   |
| `X-RateLimit-Reset`     | Unix timestamp when the window resets      |

Read `X-RateLimit-Reset` before retrying to avoid sending requests that will immediately fail.
```

--------------------------------

### Join Insights with Contacts and Companies

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/insight

Combine company-level insights with contact context by joining `per_latest`, `org_latest`, and `insights_latest`. Orders results by the last funding date.

```sql
SELECT
    c.FIRST_NAME,
    c.LAST_NAME,
    c.EMAIL_ADDRESS,
    c.JOB_TITLE,
    co.COMPANY_NAME,
    co.DOMAIN,
    i.CRM_TECH_ORG,
    i.SALES_ROLE_COUNT_ORG
FROM RELEASE.PER_LATEST c
JOIN RELEASE.ORG_LATEST co ON c.RBID_ORG = co.RBID
JOIN RELEASE.INSIGHTS_LATEST i ON c.RBID_ORG = i.RBID_ORG
ORDER BY i.LAST_FUNDING_DATE_ORG DESC;
```

--------------------------------

### Calculate Profile and Position Fill Rates

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/historical-experience

Calculate fill rates for various fields within historical experience data. This involves counting total profiles, positions, and the percentage of positions with specific fields populated.

```sql
SELECT
    COUNT(*) AS total_profiles,
    SUM(job_count) AS total_positions,
    ROUND(AVG(job_count), 1) AS avg_positions_per_profile,
    COUNT(DISTINCT linkedin_url) AS unique_profiles
FROM RELEASE.HISTORICAL_EXPERIENCE_LATEST;

-- To analyze individual positions, flatten both arrays:
SELECT
    COUNT(*) AS total_positions,
    ROUND(COUNT(job.value:rbid_org) * 100.0 / COUNT(*), 1) AS rbid_org_fill_pct,
    ROUND(COUNT(exp.value:job_title) * 100.0 / COUNT(*), 1) AS job_title_fill_pct,
    ROUND(COUNT(exp.value:job_org_name) * 100.0 / COUNT(*), 1) AS job_org_name_fill_pct,
    ROUND(COUNT(exp.value:job_function) * 100.0 / COUNT(*), 1) AS job_function_fill_pct
FROM RELEASE.HISTORICAL_EXPERIENCE_LATEST he,
LATERAL FLATTEN(input => he.jobs) job,
LATERAL FLATTEN(input => job.value:experience) exp
WHERE exp.value IS NOT NULL;
```

--------------------------------

### Handle Insufficient Permissions Error

Source: https://docs.revenuebase.ai/api-reference/v2/authentication

A `403 Forbidden` response means the API key is valid but lacks the necessary permissions for the requested endpoint. Check the key's assigned roles or permissions in the RevenueBase dashboard.

```json
{
  "detail": "Access denied for this resource"
}
```

--------------------------------

### Python: Implement Exponential Backoff for Rate Limits

Source: https://docs.revenuebase.ai/api-reference/v2/rate-limits

Use this Python function to automatically retry requests when a 429 Too Many Requests error is encountered. It implements exponential backoff to avoid overwhelming the API.

```python
import time
import requests

def call_with_backoff(url, headers, max_retries=5):
    for attempt in range(max_retries):
        response = requests.get(url, headers=headers)
        if response.status_code != 429:
            return response
        wait = 2 ** attempt  # 1s, 2s, 4s, 8s, 16s
        time.sleep(wait)
    return response
```

--------------------------------

### Process emails in batch

Source: https://docs.revenuebase.ai/api-reference/email-verification-overview

Submit a list of email addresses for batch verification. This is ideal for bulk list cleaning and pre-send scrubbing.

```APIDOC
## POST /v2/email/validate/batch

### Description
Submits a file (CSV or JSON) for batch email verification.

### Method
POST

### Endpoint
`https://api.revenuebase.ai/v2/email/validate/batch`

### Parameters
#### Request Body
- **file** (file) - Required - The CSV or JSON file containing email addresses to verify.

### Request Example
```bash
curl -X POST https://api.revenuebase.ai/v2/email/validate/batch \
  -H "x-key: {YOUR_API_KEY}" \
  -F "file=@emails.csv"
```

**Note:** This endpoint returns a `process_id` to track the job status.
```

```APIDOC
## GET /v2/jobs/{PROCESS_ID}

### Description
Polls for the status of a batch verification job.

### Method
GET

### Endpoint
`https://api.revenuebase.ai/v2/jobs/{PROCESS_ID}`

**Note:** Poll until the `status` field is `COMPLETED`.
```

```APIDOC
## GET /v2/jobs/{PROCESS_ID}/download

### Description
Downloads the results of a completed batch verification job.

### Method
GET

### Endpoint
`https://api.revenuebase.ai/v2/jobs/{PROCESS_ID}/download`

**Note:** The results are returned in the same format as the real-time verification response.
```

--------------------------------

### Historical Experience + Contacts + Companies (Alumni)

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/historical-experience

Find alumni with headquarters location data by joining historical experience, person, and organization tables. Filters for specific company URLs and non-current positions.

```sql
SELECT
    per.FIRST_NAME_PER,
    per.LAST_NAME_PER,
    per.EMAIL_ADDRESS_PER,
    exp.value:job_org_name AS former_employer,
    exp.value:job_title AS former_title,
    org.HEADQUARTERS_COUNTRY_NAME_ORG,
    org.HEADQUARTERS_CITY_ORG
FROM RELEASE.HISTORICAL_EXPERIENCE_LATEST he
JOIN RELEASE.PER_LATEST per ON he.linkedin_url = per.LINKEDIN_URL_PER
, LATERAL FLATTEN(input => he.jobs) job
, LATERAL FLATTEN(input => job.value:experience) exp
LEFT JOIN RELEASE.ORG_LATEST org ON job.value:rbid_org = org.RBID
WHERE exp.value:job_org_linkedin_url LIKE '%salesforce%'
  AND exp.value:job_is_current = FALSE
  AND per.EMAIL_ADDRESS_PER IS NOT NULL
ORDER BY per.UPDATED_AT_PER DESC;
```

--------------------------------

### Search organizations by keyword

Source: https://docs.revenuebase.ai/api-reference/v2/company-match-overview

Use discovery to find organizations matching a theme, industry, or free-text description. The `keyword` field accepts natural language.

```APIDOC
## POST /v2/organization/discover

### Description
Searches for organizations matching a keyword and optional location filters.

### Method
POST

### Endpoint
/v2/organization/discover

### Parameters
#### Request Body
- **keyword** (string) - Required - The keyword or natural language description to search for.
- **location** (string) - Optional - The location to filter results by.
- **result_count** (integer) - Optional - The number of results to return.
```

--------------------------------

### Process Email

Source: https://docs.revenuebase.ai/api-reference/overview

Verify the deliverability and detect risks associated with a single email address.

```APIDOC
## POST /v1/process-email

### Description
Verify a single email address for deliverability, role account detection, and risk assessment.

### Method
POST

### Endpoint
/v1/process-email

### Request Body
- **email** (string) - Required - The email address to verify.

### Request Example
```json
{
  "email": "test@example.com"
}
```

### Response
#### Success Response (200)
- **email** (string) - The verified email address.
- **status** (string) - The deliverability status (e.g., "deliverable", "undeliverable", "risky").
- **role** (string) - Indicates if the email is a role account (e.g., "admin", "support", "unknown").
- **risk_score** (integer) - A score indicating the risk associated with the email.
```

--------------------------------

### Score Records by Profile Freshness for Enrichment/Analytics

Source: https://docs.revenuebase.ai/docs/data-features/data-freshness/data-freshness

For enrichment and analytics, weight records by their update recency. Records updated within 90 days receive higher confidence.

```sql
-- Enrichment/analytics: weight by profile freshness (higher confidence for recent verification)
SELECT *,
       CASE
         WHEN UPDATED_AT >= DATEADD(day, -90, CURRENT_DATE()) THEN 1.0
         WHEN UPDATED_AT >= DATEADD(day, -180, CURRENT_DATE()) THEN 0.7
         ELSE 0.5
       END AS freshness_score
FROM RELEASE.PER_LATEST
ORDER BY UPDATED_AT DESC;
```

--------------------------------

### SQL Query for Companies with Insights

Source: https://docs.revenuebase.ai/docs/data-features/data-tables/organization

Fetch company details along with associated insights such as CRM technology, sales role count, CIO presence, and last funding amount. This query uses a LEFT JOIN to include all companies, even those without matching insights.

```sql
SELECT
    co.COMPANY_NAME,
    co.DOMAIN,
    co.INDUSTRY_LINKEDIN,
    co.EMPLOYEE_COUNT_MAX,
    i.CRM_TECH_ORG,
    i.SALES_ROLE_COUNT_ORG,
    i.HAS_CIO_ORG,
    i.LAST_FUNDING_AMOUNT_ORG
FROM RELEASE.ORG_LATEST co
LEFT JOIN RELEASE.INSIGHTS_LATEST i ON co.RBID = i.RBID_ORG
WHERE co.EMPLOYEE_COUNT_MAX BETWEEN 100 AND 1000;
```