> For the complete documentation index, see [llms.txt](https://docs.tajirchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tajirchain.com/api-documentation/custom-endpoints.md).

# Custom Endpoints

Some Tajir infrastructure providers may expose optional, non-standard RPC methods for advanced debugging and analytics. These endpoints are not part of the default Ethereum JSON-RPC spec and may only be available on private or self-hosted nodes.

### **What These Endpoints Provide**

* Faster or deeper block indexing
* Extended transaction tracing APIs
* Debugging and diagnostic tools for developers

***

### **Example (if enabled)**

```json
{
  "method": "debug_traceTransaction",
  "params": ["0xabc..."],
  "id": 1,
  "jsonrpc": "2.0"
}
```

***

### **Possible Custom Methods**

Availability varies by provider and node configuration.

Examples include:

| Method                     | Description                                         |
| -------------------------- | --------------------------------------------------- |
| `debug_traceTransaction`   | Returns full execution trace of a transaction       |
| `debug_traceCall`          | Traces a call without broadcasting it               |
| `debug_traceBlockByNumber` | Traces all txs in a block                           |
| `trace_replayTransaction`  | Replays a transaction with trace output             |
| `trace_block`              | Returns trace data for every transaction in a block |
| `trace_filter`             | Filter-based transaction tracing                    |

*Note: These may not be enabled on public RPC endpoints.*

### **Notes**

* Availability depends on the infrastructure provider or node operator.
* These methods are resource-intensive and may not be supported on public endpoints.
* Not recommended for production apps unless using a private node.
* Debug/trace endpoints can expose execution details that should be handled securely.