BSC Builder API — General Information¶

Overview¶

The BSC (BNB Smart Chain) Builder API delivers high-performance RPC endpoints and MEV (Maximal Extractable Value) services for developers building on BSC. Our infrastructure is engineered for low-latency, reliable access to BSC chain data and advanced transaction-ordering capabilities.

Available RPC Endpoints¶

Use the RPC endpoint below for all integrations:

Primary Endpoint: rpc.bsc.jetbldr.xyz

This endpoint uses geo DNS routing, so requests are automatically resolved to the most appropriate regional backend based on the caller's location.

Supported Methods¶

Method	Purpose
`eth_sendRawTransaction`	Standard send path — routed to the private pool by default, so wallets and SDKs need no code change.
`eth_sendBundle`	Atomic MEV bundle submission.

MEV Services¶

Builder Wallet¶

For MEV bundle submissions and transaction ordering:

Builder Address: 0xe89c42BC188c993273Ab34231e12ae60c73042E4

Important: To ensure successful bundle inclusion, transfer the bribe directly to the builder wallet. Do not rely on gasPrice modifications — they may interfere with our MEV optimization algorithms.

Example Blocks¶

Review our MEV-optimized blocks to get a feel for builder performance:

Block #39934993 — optimized transaction ordering.
Block #39927393 — MEV bundle inclusion demo.

Troubleshooting¶

Common Error Responses¶

HTTP 400 Bad Request¶

The request could not be dispatched at all.

Possible causes

The method is not one of the Supported Methods — plain-text response:
```
the method eth_getBalance does not exist/is not available
```
The body is malformed JSON, or carries no method field — same response, with an empty method name.
params has the wrong shape, such as an object where an array is expected:
```
{"error": {"code": -39400, "message": "Invalid request data"}}
```

Errors Returned with HTTP 200¶

Once a request reaches a handler, failures come back as a JSON-RPC error object with status 200 — check the response body, not just the status code.

{"id": 1, "jsonrpc": "2.0", "error": {"code": -39403, "message": "Invalid raw transaction"}}

The request id is echoed as sent, including string ids.

Support¶

For technical support and questions:

Review our comprehensive API documentation.
Check our status page for service updates.
Contact our team for enterprise solutions.