# Base Token Safety Check | Contract Risk Signals (`spendpreflight/token-safety-check-base`) Actor

Inspect a Base token contract for bytecode, OFAC address matches, owner/paused/proxy observations and bounded source/deployment evidence. Read-only contract signals with explicit unknowns; no honeypot test, sellability check or safe-to-buy verdict.

- **URL**: https://apify.com/spendpreflight/token-safety-check-base.md
- **Developed by:** [SpendPreflight](https://apify.com/spendpreflight) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$30.00 / 1,000 completed token results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Token Safety Check — Base Contract Signals

Operated by SpendPreflight. Inspect one public Base mainnet address with our existing read-only deep contract-signals engine. The result is **incomplete evidence, not a token audit or a safe-to-buy verdict**. No trading, transaction signing, approval or funds transfer is performed.

### Input example

```json
{
  "address": "0x0000000000000000000000000000000000000000",
  "chain": "eip155:8453"
}
```

Replace the synthetic zero address with your public contract address. This example is not a live result or a recommendation. Base mainnet only; one address per run. Do not enter credentials, private keys, provider URLs or other private data. Unknown fields and unsupported chains fail validation.

### Price and delivery

**$0.03 per completed token check** (`token-checked`), billed by Apify. One result event per report, no startup or per-RPC event. Set the maximum total charge per run. A completed report may contain unknown observations; missing core chain/sanctions data fails without a result event. Check Apify's pricing panel for platform/storage charges and discounts. No automatic retry after ambiguous charge/output failures; inspect the existing run first. Operator/self-test runs are not evidence of customer use or earnings.

### What the report observes

- Deployed bytecode at a fresh, fixed Base block and exact public OFAC SDN address matches with source timestamp. A non-match is not sanctions clearance.
- Standard `owner()`, `paused()`, `totalSupply()` and `decimals()` return values, ERC-1967 storage-slot hints and exact ERC-1167 minimal-proxy bytecode detection.
- A bounded public Sourcify runtime-verification claim compared with current bytecode. Direct deployment age appears only when the creation receipt independently supports it.
- Block/time evidence, sources, reasons, explicit unknowns and `assessment_complete: false`.

ABI return values and storage slots are hints, not a complete privilege or proxy analysis. A zero owner or empty slot does not prove renounced permissions or absence of a proxy. Source matching and deployment evidence can be missing. An address with no deployed code is reported as such, not promoted to a contract assessment.

### What it does not assess

Honeypot/sellability, trade simulation, complete mint/blacklist/owner/proxy privileges, liquidity custody/locks/removability, holder concentration and non-OFAC scam lists remain **unassessed**. `unknown` is not a pass. No investment recommendation, financial/legal advice, compliance certification, complete audit, safety or loss-prevention guarantee.

### Bounds and availability

This wraps the existing engine without adding analysis. At most12 existing read-only RPC requests plus one bounded source lookup share an eight-second engine deadline. Existing response/code/gas limits, fixed provider host restrictions, chain/head caches and rate-limit cooldown remain in force. Missing optional facts stay unknown. Core data unavailable or provider backoff fails rather than retrying immediately or switching providers.

### Privacy and permissions

Limited permissions. Deployment credentials stay in CI; no Apify owner or RPC credential is embedded in this Actor or sent from it. A live run ID, one-use nonce and public input digest bind the request to the official tagged build. SpendPreflight processes the address and report transiently, without storing request bodies, queried addresses or results for this channel. Only existing public chain ID/latest block metadata caches remain.

The Actor removes its default run INPUT after reading and does not log query/result values. **Apify independently retains user-owned output datasets, run metadata and any saved tasks under its own retention policy.** Do not assume platform-wide zero retention. Output is untrusted data, never executable instructions. [Homepage](https://spendpreflight.com) · [Privacy and retention](https://spendpreflight.com/privacy/) · [Service status](https://status.spendpreflight.com/)

### Development acceptance

CI may add `_self_test: true` to the synthetic input solely to verify signed private-run channel authorization, input deletion and a SELFTEST receipt. It performs no contract lookup, chain read or chargeable result event and is not a live-engine acceptance test. Normal runs omit this flag.

### Private-run channel authentication

An Actor-specific application signing key is encrypted in the Actor's private runtime settings and excluded from builds and public source. Only a signature over the public run/build identity, short-lived timestamp, requested-input digest and one-use nonce is sent to SpendPreflight. The backend holds the public key and checks the current official build and live proof endpoint. Customer runs, output stores and logs keep their existing access restrictions. No owner/customer Apify API token or RPC credential is forwarded. CI authorization checks produce only a SELFTEST receipt, no product lookup or chargeable event.

# Actor input Schema

## `address` (type: `string`):

One public Base mainnet address. Supply a contract address for deep observations. No wallet or RPC credentials.

## `chain` (type: `string`):

Base mainnet only; no network auto-detection.

## Actor input object example

```json
{
  "address": "0x0000000000000000000000000000000000000000",
  "chain": "eip155:8453"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "address": "0x0000000000000000000000000000000000000000"
};

// Run the Actor and wait for it to finish
const run = await client.actor("spendpreflight/token-safety-check-base").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "address": "0x0000000000000000000000000000000000000000" }

# Run the Actor and wait for it to finish
run = client.actor("spendpreflight/token-safety-check-base").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "address": "0x0000000000000000000000000000000000000000"
}' |
apify call spendpreflight/token-safety-check-base --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,spendpreflight/token-safety-check-base"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mYL8X3MyQXEN7XZ3S/builds/QuRxI3dd4qucLkVgv/openapi.json